- bknr-devel@common-lisp.net - mailman3.common-lisp.net

[bknr-devel] :read :update keywords meaning
by Kamen TOMOV 06 Nov '06

06 Nov '06

Hi, I tried to find in the documentation the meaning of the :read and :update slot options in define-persistent-class and I couldn't. Then I tried in the source and got lost :-) Could you please help? Thanks! -- Kamen

1 0

[bknr-devel] Merging development branch
by Tchavdar Roussanov 25 Oct '06

25 Oct '06

Hans, You have made a lot of commits to your development branch recently. Including updates to the third party tree. Do you have plans to merge these changes to the trunk? Regards, Tchavdar Roussanov

2 4

[bknr-devel] problem deleting datastore objects and multiple inheritance
by Kamen TOMOV 16 Sep '06

16 Sep '06

Hi, I have the following problem with bknr-datastore: (define-persistent-class a () ()) (define-persistent-class b () ()) (define-persistent-class c (a) ()) (define-persistent-class d (a b) ()) (delete-object (make-object 'a)) => T (delete-object (make-object 'c)) => T (delete-object (make-object 'd)) => Type-error in KERNEL::OBJECT-NOT-SIMPLE-VECTOR-ERROR-HANDLER: NIL is not of type SIMPLE-VECTOR [Condition of type TYPE-ERROR] Restarts: 0: [RETRY-TRANSACTION] Retry the transaction #<TRANSACTION 15.09.2006 15:37:18 TX-DELETE-OBJECT 75>. 1: [ABORT-REQUEST] Abort handling SLIME request. 2: [ABORT] Return to Top-Level. Backtrace: 0: ((METHOD BKNR.SKIP-LIST:SKIP-LIST-DELETE NIL (BKNR.SKIP-LIST:SKIP-LIST T)) (#(2) . #(#)) #<unused-arg> #<BKNR.SKIP-LIST:SKIP-LIST length = 15 {5A483CDD}> 75) 1: ((METHOD INDEX-REMOVE NIL (CLASS-SKIP-INDEX T)) (#(2 0 1) . #()) #<unused-arg> #<CLASS-SKIP-INDEX {5A42962D}> #<D ID: 75>) 2: ((METHOD BKNR.INDICES::DESTROY-OBJECT-WITH-CLASS NIL (INDEXED-CLASS T)) (#(17) . #()) #<unused-arg> #<PERSISTENT-CLASS D {58E9228D}> #<D ID: 75>) 3: ("DEFMETHOD EXECUTE-UNLOGGED (TRANSACTION)") 4: ("DEFCLASS MP-STORE" #<Closure Over Function "DEFMETHOD EXECUTE-UNLOGGED (TRANSACTION)" {58EB87C1}>) 5: ((METHOD BKNR.DATASTORE::EXECUTE-UNLOGGED (:AROUND) (TRANSACTION)) #<unused-arg> #S(PCL::FAST-METHOD-CALL :FUNCTION #<Closure Over Function "LAMBDA (#:G4209 #:G4210 #:G4211)" {5819E5D9}> :PV-CELL NIL :NEXT-METHOD-CALL NIL :ARG-INFO (1)) #<TRANSACTION 15.09.2006 15:37:18 TX-DELETE-OBJECT 75>) 6: ("DEFMETHOD EXECUTE-TRANSACTION (STORE TRANSACTION)") 7: ("DEFCLASS MP-STORE" #<Closure Over Function "DEFMETHOD EXECUTE-TRANSACTION (STORE TRANSACTION)" {58EB8749}>) 8: ((METHOD BKNR.DATASTORE::EXECUTE-TRANSACTION NIL (STORE TRANSACTION)) (#(0) . #(#)) #<#1=unused-arg> #<#1#> #<TRANSACTION 15.09.2006 15:37:18 TX-DELETE-OBJECT 75>) I'm using the latest bknr and CMUCL 19a-release-20040728 . Here is how the store is defined: (make-instance 'mp-store :directory "/tmp/ams-object-store/" :subsystems (list (make-instance 'store-object-subsystem)) Could please advice? Thanks! -- Kamen TOMOV

2 4

[bknr-devel] Make bknr adsf-installable
by Xan Lopez 17 May '06

17 May '06

Hi, First of all, I've recently started to use bknr in my project with great success, so thanks to all developers for their great work. I've skimmed through the list and it seems there was, or is, the intention to split bknr in several pieces (datastore from the view stuff?) and make that find its dependeces via adsf and make it adsf-installable. If you need help, I'd gladly volunteer to do that work. Cheers, Xan.

2 1

[bknr-devel] a simple kind of store
by Kamen TOMOV 16 Mar '06

16 Mar '06

Hi, The application I am working on needs a special kind of object system. What's special about it is that any store object will not ever be updated after its creation. The data would be used only for generation of reports so searching through the store should be supported. As reports would be rarely generated the objects should not be held in memory. Deletion should be supported. I was thinking of using the bknr-datastore in a following pattern: 1. Opening the data store; 2. Creation/Deletetion/Search; 3. Closing the data store. But there seem to be some obstacles: 1. As there will be a lot of entries, opening of the data store is a slow process. Too slow if we do it just to add an object; 2. This object system needs to live together with the bknr-datastore so we can't open/close no matter of the rest of the store. So what do you think? Is BKNR framework suitable for this purpose? Thanks! -- Kamen TOMOV

1 0

[bknr-devel] Commited my SBCL patches
by Tchadvar Roussanov 07 Mar '06

07 Mar '06

Hans, I just committed my sbcl patches to the trunk. My account is operational now. Please let me know if I broke something. Cheers, Tchavdar

1 0

[bknr-devel] More SBCL patches
by Tchadvar Roussanov 02 Mar '06

02 Mar '06

Hans, I've got hello-web running under SBCL 0.9.9. Attached are patches. The major change is replacement of md5 third party library with SBCL provided SB-MD5 package. Also I used xml catalog setup code from your branch. Cheers, Tchavdar

1 0

Re: [bknr-devel] Warning: Encoding destroyed object
by Kamen TOMOV 28 Feb '06

28 Feb '06

On Thu, Feb 23 2006, Hans Hübner wrote: > Hi, > > I cannot reproduce this, at least not from what you describe. The > warning is the result of a reference to a deleted object being > written to the transaction log, presumable referenced from a slot of > another object. Can you provide me with an isolated test case? Dear Hans, Sorry of not responding earlier. Here is an isolated test case: (asdf:oos 'asdf:load-op :bknr-impex) (asdf:oos 'asdf:load-op :bknr-datastore) (defpackage some-example (:use #:common-lisp #:bknr.impex #:puri #:bknr.indices #:bknr.datastore)) (in-package :some-example) (define-persistent-class obj (store-object) ()) (deftransaction del (obj) (delete-object obj)) (make-instance 'mp-store :directory "/tmp/tmp-store/" :subsystems (list (make-instance 'store-object-subsystem))) (del (make-object 'obj :name "a test" :type nil)) I noticed that if "del" is not a transaction it does not signal a warning. I am not sure why is so. Beside delete-object I would like to physically delete the file there. Thanks. Regards, -- Kamen TOMOV

2 3

[bknr-devel] Warning: Encoding destroyed object
by Kamen TOMOV 23 Feb '06

23 Feb '06

Hi, I get this warning every time I delete a blob from the store. Could you tell me why is that? Thank you. -- Kamen TOMOV

1 0

Re: [bknr-devel] SBCL port samll fixes
by Tchadvar Roussanov 14 Feb '06

14 Feb '06

Hans, In order to compile bknr/src/web/handlers.lisp with the latest cxml and sbcl, I either have to apply the change from svn to with-element macro in cxml/xml/unparse.lisp: (defmacro with-element (qname &body body) ;; XXX Statt qname soll man in zukunft auch mal (lname prefix) angeben ;; koennen. Hat aber Zeit bis DOM 2. - (when (listp qname) - (destructuring-bind (n) qname - (setf qname n))) `(invoke-with-element (lambda () ,@body) ,qname)) or change the handlers.lisp this way: (defmethod handle-object ((handler xml-object-list-handler) object req) - (cxml:with-element (xml-object-list-handler-toplevel-element-name handler) - (dolist (object (object-list-handler-get-objects handler object req)) - (object-list-handler-show-object-xml handler object req)))) + (let ((element-name (xml-object-list-handler-toplevel-element-name handler))) + (cxml:with-element element-name + (dolist (object (object-list-handler-get-objects handler object req)) + (object-list-handler-show-object-xml handler object req))))) In other words move the evaluation of xml-object-list-handler-toplevel-element-name out of the macro expansion. I think the two changes are equivalent but the second one has the advantage not to require to maintain changes to the third party library. Am I missing something? Tchavdar

1 0