Dear Team,
On Dec. 30th, Anton Kazennikov submitted the attached patch to make
Elephant work with BDB 4.6. (THANKS!) I twiddled my thumbs about it,
in part because I didn't know how many people were ready for 4.6.
It now seems that the time is ripe to make the move from 4.5 to 4
On Mon, 2008-02-25 at 15:14 +0100, Leslie P. Polzer wrote:
> Same for line 171. I wonder what's wrong?
>
I don't know why the patch didn't hash, but I was simply mistaken in not
seeing that 171 is the same; I must have gone to the wrong line number
or something. I apologize for the confusion.
I
I just pushed a patch that should automatically manage two processes
connecting to the same environment. You typically have to coordinate
who is the master user and who is the slave so that you don't try to
recover an environment that is already in use by another process.
This causes that
> just caused my Lisp to throw a warning about
>
> The slot %INDEXED-CLASS is unbound in the object # PERSISTENT-OBJECT>.
That doesn't occur when starting cleanly without FASLs, so it seems to be
a case of faulty dependency resolution or specification.
But when I open my store now, I get
debu
Ian,
the change introduced by you here:
@@ -62,8 +62,7 @@
(persistent-object (find-class 'persistent-object))
(not-already-persistent (loop for superclass in direct-superclasses
never (eq (class-of superclass)
persistent-metaclass
-
Dear Robert,
> hunk ./src/elephant/unicode2.lisp 131
> - (let ((code (char-code (schar string i
> + (let ((code (char-code (char string i
> hunk ./src/elephant/unicode2.lisp 171
> - (let ((code (char-code (schar string i
> +
Dear Leslie,
In attempting to apply the second of your three patches
(unicode2.patch), darcs says:
[EMAIL PROTECTED] elephant]$ darcs apply ../unicode2.patch
darcs failed: Patch bundle failed hash!
This probably means that the patch has been corrupted by a mailer.
The most likely culpri
> To isolate the problem, can you verify the base case, connect two
> images to a fresh db?
Here's one for SQLite:
(asdf:oos 'asdf:load-op 'elephant)
(defpackage #:ele-test (:use :cl :elephant))
(in-package :ele-test)
(defpclass myclass ()
((testslot :accessor testslot :initarg testslot :i
> To isolate the problem, can you verify the base case, connect two
> images to a fresh db?
For BDB:
(asdf:oos 'asdf:load-op 'elephant)
(defpackage #:ele-test (:use :cl :elephant))
(in-package :ele-test)
(defpclass myclass ()
((testslot :accessor testslot :initarg testslot :index t)))
(op
On Feb 25, 2008, at 4:00 AM, Alex Mizrahi wrote:
[EMAIL PROTECTED]:~$ psql -c "create language plpgsql" elepm
ERROR: must be superuser to create procedural language
I think this is changed in 8.3 -- you don't have to be superuser to
create a trusted language.
John DeSoi, Ph.D.
_
LPP> At the moment this has to be done for each Postgres database used
LPP> by Elephant. Any objections on doing this automatically if needed?
we have this:
(defun init-stored-procedures (con)
(safe-ignore-postgres-error (con)
(cl-postgres:exec-query con "CREATE LANGUAGE plpgsql;"))
but
Yes, because it doesn't work for postgres 8.2 in all cases, probably
because of security settings. I know we have been trying that before,
and there was at least a reason it was left out... But if you can make
it work under a check for postgres 8.3 that is great..
/ Henrik
2008/2/25, Leslie P. Pol
12 matches
Mail list logo
