AM> so i'll describe profiling results here -- what's fast and what's not
AM> with postmodern backend.
probably i also need some kind of conclusion..
so, db-postmodern seems to work fine when it's used with persistent
instances of classes, and only basic queries (get-instance-by-value,
get-in
hello
unfortunately rewrite of pm-cursor implementation is postponed for now, it
turned to be more complex than it seemed originally. and i do not have test
cases anyway..
however i've made a patch that improves performance of
get-instances-by-value (i've sent it to Henrik so it should be avail
How would I go about doing a live backup of an Elephant-persistent
set of objects? I suppose just copying the Berkeley DB would result
in inconsistencies...
Leslie
___
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/ma
There really isn't a good solution to this that I'm aware of other
than a stop and copy. The easiest would be to halt all transactions,
do a file system copy, then continue. That might only take a handful
of seconds depending on the size of your DB and speed of your system.
There are more
Hi Alex & all,
1) In general we seem to have data stores that have different sweet
spots and different optimal uses of an API. We probably should come
up with a Matrix of features and suggested uses for each of them.
This includes what types are in lisp-sort-order and which are not for
Ian Eslick <[EMAIL PROTECTED]> writes:
> What prospects are there for having a reasonable map implementation in
> postmodern?
Surely the prospects must be good; it's not very different
from what Lispworks' CommonSQL does with MAP-QUERY.
> 4) btrees are lightweight in BDB, but heavy in SQL - sou
IE> 2) In retrospect it was a mistake to expose the cursor API to the
IE> users, but Elephant started as a low-level interface to BDB with some
IE> minimal support for persistent objects and has grown from there so at
IE> the time it made sense. I recommend we consider deprecating the
IE> cur
Dear Elephant developers,
I'm trying to develop an application using Elephant, and
I think I've settled on the POSTMODERN back end.
Now, part of the application maps very naturally in what Elephant can
do, and other parts of it map better onto raw SQL processing,
where I wish to use POSTMODERN m
