Actually, when we put darcs in place, I think it will be easier to
support a branch-and-merge
strategy that should inflict less pain on the would be users; but I
would like to thank Ian
and all of the people who have tested for getting us this far allow.
On Fri, 2007-03-09 at 21:51 -0500, Ian Es
Sorry about that - some of the recent cvs instability is my fault.
I've had some premature checkins. I currently am green on the non-
migration backend tests for SBCL and ACL on Mac OS. I'm fixing the
open migration issues today and tomorrow including beefing up the
test suite for various
Very cool! When we finish 0.6.1, we can throw it into the new darcs
development tree as part of the 0.7.0 release plan. You might write
some Trac tickets against it (what needs to be done to put it into a
release, etc) so we can keep track of it.
Did you learn anything about elephant that
Wow. That is EXTREMELY cool!
I will try to look at it this weekend. Thank you very much!
On Fri, 2007-03-09 at 18:31 +0100, Henrik Hjelte wrote:
> I have made a new elephant backend, db-postmodern.
> It uses postgresql for storage, and the postmodern lisp socket interface
> instead of clsql. T
I have made a new elephant backend, db-postmodern.
It uses postgresql for storage, and the postmodern lisp socket interface
instead of clsql. The implementation is actually quite different from
the clsql backend.
db-postmodern uses prepared queries and stored procedures for
performance reasons.
Here are some observations on the latest cvs version.
/Henrik Hjelte
Testmigration, line 182:
(:dbcn-spc-pst (elephant::%index-cache (find-class 'ipfoo)
should be:
(elephant::dbcn-spc-pst (elephant::%index-cache (find-class 'ipfoo)
Also, bdb doesn't compile on linux/sbcl/amd64:
; $ gcc
