OK, I have applied this patch.
I didn't run the tests. Ordinarily I do before accepting a patch, but
I assume if this causes a problem we will catch it quickly in our
current state.
Of course, please make sure you are all green before submitting a patch.
On Mon, 2008-05-05 at 14:07 +0200, Les
Robert and I have agreed about moving Elephant towards a 1.0 release.
Elephant isn't perfect, but more and more people appear to be having
success using it and we feel this kind of predictability is important
for its ongoing adoption. The purpose of this 1.0 release is to
provide a stable
Awesome! Thank you Robert.
Henrik? Alex?
Ian
On May 4, 2008, at 10:50 PM, Robert L. Read wrote:
I have now committed an all-green solution for the CL-SQL backend to
elephant-unstable.
I don't know that it will help the Postmodern work much --- perhaps
just
as a pointer for what needs to
LPP> When an error occurs inside a txn, this restart will lose the
LPP> controller. It should be replaced by the ABORT-TRANSACTION restart
LPP> behaviour.
sorry, i didn't get -- what is "ABORT restart", how does it lose the
controller and how are you going to remove it?
___
Ian Eslick wrote:
Definitely work elephant-unstable if you want to test the new
functionality. Most of the activity in the main branch has been in
and around the postmodern interface. The limiting factor in merging
the branches is getting support for the new data store API (i.e. for
btrees w
When an error occurs inside a txn, this restart will lose the controller.
It should be replaced by the ABORT-TRANSACTION restart behaviour.
Anyone against this?
Leslie
___
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.n
LPP> you explained that global-sync cache mode only works within a txn.
LPP> I thought that per-transaction cache mode does this, and that global
LPP> sync extends this behaviour so transactions/threads can share the
LPP> cache?
LPP> If not, what's the difference between them?
both modes rely
Now don't ask me how a NIL value gets mapped to an OID key in the
class index. It happened, and I wasn't able to remove those things
because of a bug in PM-INDEXED-BTREE. Diff:
--- old-elephant/src/db-postmodern/pm-indexed-btree.lisp2008-05-05
14:04:49.930108544 +0200
+++ new-elephant/src
Sorting on a slot field with NIL values and START, END = NIL
doesn't work correctly:
MYSTIC(23): (defpclass moo () ((slot1 :type list :initform nil :index t)))
#
MYSTIC(24): (make-instance 'moo)
#
MYSTIC(25): (get-instances-by-class 'moo)
(#)
MYSTIC(26): (get-instances-by-range 'moo 'slot1 nil
Alex,
you explained that global-sync cache mode only works within a txn.
I thought that per-transaction cache mode does this, and that global
sync extends this behaviour so transactions/threads can share the
cache?
If not, what's the difference between them?
Leslie
__
I guess we don't need this patch anymore in unstable, so it's moot to
apply it. If for any reason you'd like to do this nevertheless,
don't use this patch; I have an updated version that works correctly.
If not, just ignore this.
Leslie
___
elephant-
11 matches
Mail list logo
