At the moment this has to be done for each Postgres database used
by Elephant. Any objections on doing this automatically if needed?
Leslie
___
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-d
> Why don't you send over stack traces and a more in-depth description
> of your setup.
Here's the BDB case.
Underlying setup is the same as in the SQLite scenario. Backtrace inline
at the bottom of this message (irrelevant parts cut).
I have a game engine and an administration backend, which a
> Why don't you send over stack traces and a more in-depth description
> of your setup.
Here's the SQLite story.
I'm using SQLite3 version 3.5.6 (apparently compiled with thread safety),
CLSQL 4.0.1, SBCL 1.0.14 and the latest Elephant on an ext3 file system,
kernel 2.6.24.
The error occurs on
I just opened a fresh DB from both an Allegro image and an SBCL image
with no problems, set some data in one and read it from the other.
This fails for you? I believe other people are using multiple images
on multi-processor machines without incident so this may be a
configuration or envi
I just got this:
While accessing database #
with expression "UPDATE KEYVALUE SET KEY =
'DysNCQYAAABQT1RJT04JBgAAAE1ZU1RJQw==',CLCTN_ID = 28,VALUE =
'DQkBVAkLAAA
AQ09NTU9OLUxJU1A=' WHERE ((CLCTN_ID = 28) AND (KEY =
'DysNCQYAAABQT1RJT04JBgAAAE1ZU1RJQw=='))":
Error 5 / database is l
