Alex's recent question about why dup-btrees were persistent-metaclass
along with a project of my own led me to the previously reported bug
about deserializing btrees that had a nil in the oid slot. This is
related to the reason that dup-btrees were originally persistent-
metaclass.
The
I'm using BDB 4.6 with this my-config.sexp
;; Linux defaults
#+(and (or sbcl allegro openmcl lispworks) (not (or mswindows
windows)) (not (or macosx darwin)))
((:compiler . :gcc)
(:berkeley-db-version . "4.6")
(:berkeley-db-include-dir . "/usr/include/")
(:berkeley-db-lib-dir . "/usr/lib/")
(:
When the Trac web interface is back online, we can keep a list of
todo's there as part of the bug tracking system.
We also need to test upgrade from 0.9.1.
I forget if we had figured out what to call this release. Opinions?
Ian
On Jun 2, 2008, at 5:43 PM, Ian Eslick wrote:
Fantastic! Than
Fantastic! Thanks for all the work on this. Now I have no excuse to
start the long list of little items necessary to get to a release...
The big areas are:
- Thread safety for all schema-related operations
- Test coverage
- Docs coverage
Some bugs I've seen and haven't been able to fix:
- Le
IE> Sounds like there is an issue with schema coherence (the class object
IE> cache out of sync with the db in some way? I had some of these tuning
IE> the BDB implementation).
i've found the issue -- postmodern backend creates its "system" btrees
(like root, schema-table etc) in "fancy" way,
Just to ask the basic questions. Which BDB are you using and does
your my-config.sexp match that version?
Ian
On Jun 1, 2008, at 11:44 PM, Leonardo Varuzza wrote:
Hello,
If I change the declaim in the top of berkeley-db.lisp to (safety 3)
(debug 3), I got this error from SBCL 1.0.17 on AMD
I'm not sure of the history of this distinction - but I updated the
API to use drop-instance and drop-instances. I also exported drop-
instance-slots to delete persistent storage without dropping/
invalidating the instance itself.
Ian
On Jun 2, 2008, at 5:04 AM, Leslie P. Polzer wrote:i
Err, any specific reason why we have DROP-POBJECT and DROP-INSTANCES?
It would be more orthogonal to have one function for deleting objects.
Leslie
___
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/e
