From franks-muc at web.de  Sun Jan  3 12:51:27 2010
From: franks-muc at web.de (Frank Schorr)
Date: Sun, 03 Jan 2010 13:51:27 +0100
Subject: [elephant-devel] upgrade from 0.9 to 1.0
Message-ID: <2098983249@web.de>

Hi Ian:

I'm currently revising my software and thought I should also upgrade my elephant from 0.9 to 1.0 
using lispworks on win32.

Compiling was easy, apart from two problems related to base-string:

Error: BASE-STRING is not the name of a class
when compiling walk-heap in in elephant-1.0/src/elephant/gc.lisp
I commented out the method for base-string

Error while reading: Saw character U+0080 with syntax type invalid. 
when compiling  deftest base-strings in elephant-1.0/tests/testserializer.lisp
I commented out the deftest form

But calling open-store on a fresh postgres database does not work.
 
I removed the handler-case in (defun deserialize ... in serializer.lisp to let the debuger go down and compiled serializer2.lisp with (debug 3) to produce the backtrace below.
There seems to be one issue with the initarg for the condition. 
But the problem is that error is called at the t clause of the big cond, and I have no idea how to track this down any further .

What can I do to improve elephant 1.0 for Lispworks/win ?

Best regards
Frank




Error: The error 'MAKE-INSTANCE is called with keyword :TAG among the arguments (ELEPHANT-TYPE-DESERIALIZATION-ERROR :TAG 0) which is not one of (:CONDITION ELEPHANT::TYPE-TAG).'
was raised while coercing (ELEPHANT-TYPE-DESERIALIZATION-ERROR :TAG 0) to a condition.
  1 (continue) retry db-postmodern transaction
  2 DB-POSTMODERN::ABORT-TRANSACTION
  3 (abort) Abort job 5 :(BIND-STANDARD-STREAMS-AND-EXECUTE #<EDITOR::EDITOR-OUTPUT-STREAM #<EDITOR:BUFFER Background Output> 21863E3F> (FUNCALL-BACKGROUND-JOB-AUX #<CAPI:EDITOR-PANE CAPI:EDITOR-PANE  21AF8C8B> BACKGROUND-REGION-EVAL (# # # # T NIL NIL)))

Type :b for backtrace, :c <option number> to proceed,  or :? for other options

CL-USER 1 : 1 > :b :verbose
Call to (SUBFUNCTION (LABELS ELEPHANT-SERIALIZER2::%DESERIALIZE) ELEPHANT-SERIALIZER2::DESERIALIZE) (offset 2164)
  ELEPHANT-SERIALIZER2::BS                   : #S(ELEPHANT-MEMUTIL:BUFFER-STREAM :BUFFER #<Pointer to type (:UNSIGNED :CHAR) = #x0039FFB0> :SIZE 45 :POSITION 2844 :LENGTH 80)
  ELEPHANT-SERIALIZER2::BS                   : #S(ELEPHANT-MEMUTIL:BUFFER-STREAM :BUFFER #<Pointer to type (:UNSIGNED :CHAR) = #x0039FFB0> :SIZE 45 :POSITION 2844 :LENGTH 80)
  ELEPHANT-SERIALIZER2::TAG                  : 17
  ELEPHANT-SERIALIZER2::ID                   : 0
  ELEPHANT-SERIALIZER2::MAYBE-HASH           : NIL
  DBG::|internal-flet-name-for-LOOKUP-ID|    : #<Closure (ELEPHANT-SERIALIZER2::DESERIALIZE LABELS ELEPHANT-SERIALIZER2::LOOKUP-ID) 218FE0FA>
  DBG::|internal-flet-name-for-ADD-OBJECT|   : #<Closure (ELEPHANT-SERIALIZER2::DESERIALIZE LABELS ELEPHANT-SERIALIZER2::ADD-OBJECT) 218FE112>
  DBG::|internal-flet-name-for-%DESERIALIZE| : #<Closure (ELEPHANT-SERIALIZER2::DESERIALIZE LABELS ELEPHANT-SERIALIZER2::%DESERIALIZE) 218FE0CA>
  ELEPHANT-SERIALIZER2::SC                   : #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
  ELEPHANT-SERIALIZER2::OID-ONLY             : NIL

Call to ELEPHANT-SERIALIZER2::DESERIALIZE (offset 375)
  ELEPHANT-SERIALIZER2::BUF-STR              : #S(ELEPHANT-MEMUTIL:BUFFER-STREAM :BUFFER #<Pointer to type (:UNSIGNED :CHAR) = #x0039FFB0> :SIZE 45 :POSITION 2844 :LENGTH 80)
  ELEPHANT-SERIALIZER2::SC                   : #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
  ELEPHANT-SERIALIZER2::OID-ONLY             : NIL
  DBG::OID-ONLY                              : T
  ELEPHANT-SERIALIZER2::BUF-STR              : #S(ELEPHANT-MEMUTIL:BUFFER-STREAM :BUFFER #<Pointer to type (:UNSIGNED :CHAR) = #x0039FFB0> :SIZE 45 :POSITION 2844 :LENGTH 80)
  ELEPHANT-SERIALIZER2::OID-ONLY             : NIL
  ELEPHANT-SERIALIZER2::CIRCULARITY-VECTOR   : #()
  DBG::|internal-flet-name-for-%DESERIALIZE| : #<Closure (ELEPHANT-SERIALIZER2::DESERIALIZE LABELS ELEPHANT-SERIALIZER2::%DESERIALIZE) 218FE0CA>
  DBG::|internal-flet-name-for-ADD-OBJECT|   : #<Closure (ELEPHANT-SERIALIZER2::DESERIALIZE LABELS ELEPHANT-SERIALIZER2::ADD-OBJECT) 218FE112>
  DBG::|internal-flet-name-for-LOOKUP-ID|    : #<Closure (ELEPHANT-SERIALIZER2::DESERIALIZE LABELS ELEPHANT-SERIALIZER2::LOOKUP-ID) 218FE0FA>

Call to DB-POSTMODERN::DESERIALIZE-FROM-DATABASE (offset 63)
  DB-POSTMODERN::X         : #(17 0 0 0 0 13 9 3 0 0 0 69 81 76 9 11 0 0 0 67 79 77 77 79 78 45 76 73 83 80 4 0 0 0 64 4 0 0 128 63 ...)
  DB-POSTMODERN::SC        : #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
  DB-POSTMODERN::OIDS-ONLY : NIL
  DB-POSTMODERN::OTHER     : #S(ELEPHANT-MEMUTIL:BUFFER-STREAM :BUFFER #<Pointer to type (:UNSIGNED :CHAR) = #x0039FFB0> :SIZE 45 :POSITION 2844 :LENGTH 80)

Call to (METHOD DB-POSTMODERN::INTERNAL-GET-VALUE (T DB-POSTMODERN::PM-BTREE)) (offset 369)
  DB-POSTMODERN::KEY          : "3 INDICES"
  DB-POSTMODERN::BT           : #<DB-POSTMODERN::PM-BTREE db-table:slots 2133F92F>
  CLOS::.ISL.                 : :DONT-KNOW
  DB-POSTMODERN::VALUE        : NIL
  DB-POSTMODERN::EXISTS-P     : NIL
  DB-POSTMODERN::*SC*         : #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
  DB-POSTMODERN::*CONNECTION* : #<CL-POSTGRES:DATABASE-CONNECTION 2134C41F>
  DB-POSTMODERN::RESULT       : #(17 0 0 0 0 13 9 3 0 0 0 69 81 76 9 11 0 0 0 67 79 77 77 79 78 45 76 73 83 80 4 0 0 0 64 4 0 0 128 63 ...)

Call to (METHOD GET-VALUE (T DB-POSTMODERN::PM-BTREE)) (offset 20)
  DB-POSTMODERN::KEY : "3 INDICES"
  DB-POSTMODERN::BT  : #<DB-POSTMODERN::PM-BTREE db-table:slots 2133F92F>
  CLOS::.ISL.        : :DONT-KNOW

Call to (METHOD ELEPHANT::PERSISTENT-SLOT-READER (DB-POSTMODERN::POSTMODERN-STORE-CONTROLLER T T)) (offset 78)
  DB-POSTMODERN::SC        : #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
  DB-POSTMODERN::INSTANCE  : #<DB-POSTMODERN::PM-INDEXED-BTREE db-table:schemas 2138F01B>
  DB-POSTMODERN::NAME      : DB-POSTMODERN::INDICES
  DB-POSTMODERN::OIDS-ONLY : :DONT-KNOW
  CLOS::.ISL.              : :DONT-KNOW
  DB-POSTMODERN::*SC*      : #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>

Call to CLOS::METHOD-COMBINATION-TEMPLATE (offset 45)

Call to (METHOD CLOS::DYNAMIC-SLOT-VALUE-USING-SLOTD (T T)) (offset 120)
  CLOS::INSTANCE : #<DB-POSTMODERN::PM-INDEXED-BTREE db-table:schemas 2138F01B>
  CLOS::SLOTD    : #<ELEPHANT::PERSISTENT-EFFECTIVE-SLOT-DEFINITION DB-POSTMODERN::INDICES 21369C9B>

Call to (METHOD GET-INDEX (DB-POSTMODERN::PM-INDEXED-BTREE T)) (offset 16)
  DB-POSTMODERN::BT         : #<DB-POSTMODERN::PM-INDEXED-BTREE db-table:schemas 2138F01B>
  DB-POSTMODERN::INDEX-NAME : ELEPHANT::BY-NAME
  CLOS::.ISL.               : :DONT-KNOW

Call to (METHOD ELEPHANT::ENSURE-INDEX (INDEXED-BTREE T)) (offset 27)

Call to (SUBFUNCTION 2 (METHOD ELEPHANT::OPEN-CONTROLLER :AFTER (STORE-CONTROLLER))) (offset 65)

Call to DB-POSTMODERN::EXECUTE-TRANSACTION-ONE-TRY (offset 169)
  DB-POSTMODERN::SC                : #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
  DB-POSTMODERN::TXN-FN            : #<Closure ((METHOD ELEPHANT::OPEN-CONTROLLER :AFTER (STORE-CONTROLLER)) . 2) 21378012>
  DB-POSTMODERN::ALWAYS-ROLLBACK   : NIL
  DB-POSTMODERN::TRAN              : #<POSTMODERN::TRANSACTION-HANDLE 21382FE3>
  DB-POSTMODERN::COMMITED          : NIL
  DB-POSTMODERN::*TXN-VALUE-CACHE* : NIL

Call to (METHOD ELEPHANT::EXECUTE-TRANSACTION (DB-POSTMODERN::POSTMODERN-STORE-CONTROLLER T)) (offset 889)
  DB-POSTMODERN::SC               : #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
  DB-POSTMODERN::TXN-FN           : #<Closure ((METHOD ELEPHANT::OPEN-CONTROLLER :AFTER (STORE-CONTROLLER)) . 2) 21378012>
  DBG::G                          : :DONT-KNOW
  DB-POSTMODERN::ALWAYS-ROLLBACK  : NIL
  DB-POSTMODERN::RETRY-CLEANUP-FN : NIL
  DB-POSTMODERN::RETRIES          : 200
  CLOS::.ISL.                     : :DONT-KNOW
  POSTMODERN:*DATABASE*           : #<CL-POSTGRES:DATABASE-CONNECTION 2134C41F>
  DB-POSTMODERN::TRY              : 200
  DBG::G                          : #<Closure ((METHOD ELEPHANT::EXECUTE-TRANSACTION (DB-POSTMODERN::POSTMODERN-STORE-CONTROLLER T)) . 5) 2137802A>
  DBG::G                          : #<Function ((METHOD ELEPHANT::EXECUTE-TRANSACTION (DB-POSTMODERN::POSTMODERN-STORE-CONTROLLER T)) . 4) 213026A2>
  DBG::G                          : #<Closure ((METHOD ELEPHANT::EXECUTE-TRANSACTION (DB-POSTMODERN::POSTMODERN-STORE-CONTROLLER T)) . 3) 21378042>
  CONDITIONS::*RESTART-CLUSTERS*  : ((#<RESTART ABORT 218FD567>) (#<RESTART ABORT 218FD7CF>) (#<RESTART DB-POSTMODERN::RETRY-TRANSACTION 21345197> #<RESTART DB-POSTMODERN::ABORT-TRANSACTION 213451BB>) (#<RESTART ABORT 213451DF>) (#<RESTART ABORT 21B1398B>))
  DBG::G                          : #<Function ((METHOD ELEPHANT::EXECUTE-TRANSACTION (DB-POSTMODERN::POSTMODERN-STORE-CONTROLLER T)) . 8) 2130275A>
  CONDITIONS::*HANDLER-CLUSTERS*  : (((CL-POSTGRES:DATABASE-ERROR . #<Function # 2130275A>)) ((WARNING . EDITOR::EDITOR-EVALUATION-WARNING)) ((END-OF-FILE . #<Closure # 2135380A>) (READER-ERROR . #<Closure # 218FEA32>)))

Call to CLOS::METHOD-COMBINATION-TEMPLATE (offset 146)

Call to CLOS::NEXT-METHOD-CALL-2 (offset 87)
  CONS               : (METHOD ELEPHANT::OPEN-CONTROLLER :AROUND (DB-POSTMODERN::POSTMODERN-STORE-CONTROLLER))
  CLOS::NEXT-METHODS : (#<Closure CLOS::METHOD-COMBINATION-TEMPLATE 2133B46A>)
  #:G174431          : #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
  #:G174432          : NIL

Call to (METHOD ELEPHANT::OPEN-CONTROLLER :AROUND (DB-POSTMODERN::POSTMODERN-STORE-CONTROLLER)) (offset 61)
  DB-POSTMODERN::SC          : #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
  DBG::G                     : NIL
  CLOS::.ISL.                : :DONT-KNOW
  DBG::G                     : (#<Closure CLOS::METHOD-COMBINATION-TEMPLATE 2133B46A>)
  DB-POSTMODERN:*CACHE-MODE* : NIL

Call to CLOS::METHOD-COMBINATION-TEMPLATE (offset 42)

Call to OPEN-STORE (offset 66)

Call to EVAL (offset 113)
  EXP : (OPEN-STORE *DB-SPEC*)

Call to EDITOR::EDITOR-EVAL (offset 177)
  EDITOR:BUFFER  : :DONT-KNOW
  EDITOR::SEXP   : (OPEN-STORE *DB-SPEC*)
  EDITOR::ERRORP : T

______________________________________________________
GRATIS f?r alle WEB.DE-Nutzer: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://movieflat.web.de




From eslick at media.mit.edu  Sun Jan  3 22:36:06 2010
From: eslick at media.mit.edu (Ian Eslick)
Date: Sun, 3 Jan 2010 14:36:06 -0800
Subject: [elephant-devel] upgrade from 0.9 to 1.0
In-Reply-To: <2098983249@web.de>
References: <2098983249@web.de>
Message-ID: <412DD00C-B9A5-44E5-9354-CB66CBFB4B4F@media.mit.edu>

Hi Frank,

Have you tested with BDB?  I'm curious if it's a backend issue (the serialized byte-stream seems to be at fault; it's what's causing the condition to be asserted which itself fails).  

The other sanity check is to confirming no stale fasls and appropriate settings in my-config.sexp

I can probably take a look at this in depth this coming weekend, but I'm probably too busy this week.

Thank you,
Ian

On Jan 3, 2010, at 4:51 AM, Frank Schorr wrote:

> Hi Ian:
> 
> I'm currently revising my software and thought I should also upgrade my elephant from 0.9 to 1.0 
> using lispworks on win32.
> 
> Compiling was easy, apart from two problems related to base-string:
> 
> Error: BASE-STRING is not the name of a class
> when compiling walk-heap in in elephant-1.0/src/elephant/gc.lisp
> I commented out the method for base-string
> 
> Error while reading: Saw character U+0080 with syntax type invalid. 
> when compiling  deftest base-strings in elephant-1.0/tests/testserializer.lisp
> I commented out the deftest form
> 
> But calling open-store on a fresh postgres database does not work.
> 
> I removed the handler-case in (defun deserialize ... in serializer.lisp to let the debuger go down and compiled serializer2.lisp with (debug 3) to produce the backtrace below.
> There seems to be one issue with the initarg for the condition. 
> But the problem is that error is called at the t clause of the big cond, and I have no idea how to track this down any further .
> 
> What can I do to improve elephant 1.0 for Lispworks/win ?
> 
> Best regards
> Frank
> 
> 
> 
> 
> Error: The error 'MAKE-INSTANCE is called with keyword :TAG among the arguments (ELEPHANT-TYPE-DESERIALIZATION-ERROR :TAG 0) which is not one of (:CONDITION ELEPHANT::TYPE-TAG).'
> was raised while coercing (ELEPHANT-TYPE-DESERIALIZATION-ERROR :TAG 0) to a condition.
>  1 (continue) retry db-postmodern transaction
>  2 DB-POSTMODERN::ABORT-TRANSACTION
>  3 (abort) Abort job 5 :(BIND-STANDARD-STREAMS-AND-EXECUTE #<EDITOR::EDITOR-OUTPUT-STREAM #<EDITOR:BUFFER Background Output> 21863E3F> (FUNCALL-BACKGROUND-JOB-AUX #<CAPI:EDITOR-PANE CAPI:EDITOR-PANE  21AF8C8B> BACKGROUND-REGION-EVAL (# # # # T NIL NIL)))
> 
> Type :b for backtrace, :c <option number> to proceed,  or :? for other options
> 
> CL-USER 1 : 1 > :b :verbose
> Call to (SUBFUNCTION (LABELS ELEPHANT-SERIALIZER2::%DESERIALIZE) ELEPHANT-SERIALIZER2::DESERIALIZE) (offset 2164)
>  ELEPHANT-SERIALIZER2::BS                   : #S(ELEPHANT-MEMUTIL:BUFFER-STREAM :BUFFER #<Pointer to type (:UNSIGNED :CHAR) = #x0039FFB0> :SIZE 45 :POSITION 2844 :LENGTH 80)
>  ELEPHANT-SERIALIZER2::BS                   : #S(ELEPHANT-MEMUTIL:BUFFER-STREAM :BUFFER #<Pointer to type (:UNSIGNED :CHAR) = #x0039FFB0> :SIZE 45 :POSITION 2844 :LENGTH 80)
>  ELEPHANT-SERIALIZER2::TAG                  : 17
>  ELEPHANT-SERIALIZER2::ID                   : 0
>  ELEPHANT-SERIALIZER2::MAYBE-HASH           : NIL
>  DBG::|internal-flet-name-for-LOOKUP-ID|    : #<Closure (ELEPHANT-SERIALIZER2::DESERIALIZE LABELS ELEPHANT-SERIALIZER2::LOOKUP-ID) 218FE0FA>
>  DBG::|internal-flet-name-for-ADD-OBJECT|   : #<Closure (ELEPHANT-SERIALIZER2::DESERIALIZE LABELS ELEPHANT-SERIALIZER2::ADD-OBJECT) 218FE112>
>  DBG::|internal-flet-name-for-%DESERIALIZE| : #<Closure (ELEPHANT-SERIALIZER2::DESERIALIZE LABELS ELEPHANT-SERIALIZER2::%DESERIALIZE) 218FE0CA>
>  ELEPHANT-SERIALIZER2::SC                   : #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
>  ELEPHANT-SERIALIZER2::OID-ONLY             : NIL
> 
> Call to ELEPHANT-SERIALIZER2::DESERIALIZE (offset 375)
>  ELEPHANT-SERIALIZER2::BUF-STR              : #S(ELEPHANT-MEMUTIL:BUFFER-STREAM :BUFFER #<Pointer to type (:UNSIGNED :CHAR) = #x0039FFB0> :SIZE 45 :POSITION 2844 :LENGTH 80)
>  ELEPHANT-SERIALIZER2::SC                   : #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
>  ELEPHANT-SERIALIZER2::OID-ONLY             : NIL
>  DBG::OID-ONLY                              : T
>  ELEPHANT-SERIALIZER2::BUF-STR              : #S(ELEPHANT-MEMUTIL:BUFFER-STREAM :BUFFER #<Pointer to type (:UNSIGNED :CHAR) = #x0039FFB0> :SIZE 45 :POSITION 2844 :LENGTH 80)
>  ELEPHANT-SERIALIZER2::OID-ONLY             : NIL
>  ELEPHANT-SERIALIZER2::CIRCULARITY-VECTOR   : #()
>  DBG::|internal-flet-name-for-%DESERIALIZE| : #<Closure (ELEPHANT-SERIALIZER2::DESERIALIZE LABELS ELEPHANT-SERIALIZER2::%DESERIALIZE) 218FE0CA>
>  DBG::|internal-flet-name-for-ADD-OBJECT|   : #<Closure (ELEPHANT-SERIALIZER2::DESERIALIZE LABELS ELEPHANT-SERIALIZER2::ADD-OBJECT) 218FE112>
>  DBG::|internal-flet-name-for-LOOKUP-ID|    : #<Closure (ELEPHANT-SERIALIZER2::DESERIALIZE LABELS ELEPHANT-SERIALIZER2::LOOKUP-ID) 218FE0FA>
> 
> Call to DB-POSTMODERN::DESERIALIZE-FROM-DATABASE (offset 63)
>  DB-POSTMODERN::X         : #(17 0 0 0 0 13 9 3 0 0 0 69 81 76 9 11 0 0 0 67 79 77 77 79 78 45 76 73 83 80 4 0 0 0 64 4 0 0 128 63 ...)
>  DB-POSTMODERN::SC        : #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
>  DB-POSTMODERN::OIDS-ONLY : NIL
>  DB-POSTMODERN::OTHER     : #S(ELEPHANT-MEMUTIL:BUFFER-STREAM :BUFFER #<Pointer to type (:UNSIGNED :CHAR) = #x0039FFB0> :SIZE 45 :POSITION 2844 :LENGTH 80)
> 
> Call to (METHOD DB-POSTMODERN::INTERNAL-GET-VALUE (T DB-POSTMODERN::PM-BTREE)) (offset 369)
>  DB-POSTMODERN::KEY          : "3 INDICES"
>  DB-POSTMODERN::BT           : #<DB-POSTMODERN::PM-BTREE db-table:slots 2133F92F>
>  CLOS::.ISL.                 : :DONT-KNOW
>  DB-POSTMODERN::VALUE        : NIL
>  DB-POSTMODERN::EXISTS-P     : NIL
>  DB-POSTMODERN::*SC*         : #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
>  DB-POSTMODERN::*CONNECTION* : #<CL-POSTGRES:DATABASE-CONNECTION 2134C41F>
>  DB-POSTMODERN::RESULT       : #(17 0 0 0 0 13 9 3 0 0 0 69 81 76 9 11 0 0 0 67 79 77 77 79 78 45 76 73 83 80 4 0 0 0 64 4 0 0 128 63 ...)
> 
> Call to (METHOD GET-VALUE (T DB-POSTMODERN::PM-BTREE)) (offset 20)
>  DB-POSTMODERN::KEY : "3 INDICES"
>  DB-POSTMODERN::BT  : #<DB-POSTMODERN::PM-BTREE db-table:slots 2133F92F>
>  CLOS::.ISL.        : :DONT-KNOW
> 
> Call to (METHOD ELEPHANT::PERSISTENT-SLOT-READER (DB-POSTMODERN::POSTMODERN-STORE-CONTROLLER T T)) (offset 78)
>  DB-POSTMODERN::SC        : #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
>  DB-POSTMODERN::INSTANCE  : #<DB-POSTMODERN::PM-INDEXED-BTREE db-table:schemas 2138F01B>
>  DB-POSTMODERN::NAME      : DB-POSTMODERN::INDICES
>  DB-POSTMODERN::OIDS-ONLY : :DONT-KNOW
>  CLOS::.ISL.              : :DONT-KNOW
>  DB-POSTMODERN::*SC*      : #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
> 
> Call to CLOS::METHOD-COMBINATION-TEMPLATE (offset 45)
> 
> Call to (METHOD CLOS::DYNAMIC-SLOT-VALUE-USING-SLOTD (T T)) (offset 120)
>  CLOS::INSTANCE : #<DB-POSTMODERN::PM-INDEXED-BTREE db-table:schemas 2138F01B>
>  CLOS::SLOTD    : #<ELEPHANT::PERSISTENT-EFFECTIVE-SLOT-DEFINITION DB-POSTMODERN::INDICES 21369C9B>
> 
> Call to (METHOD GET-INDEX (DB-POSTMODERN::PM-INDEXED-BTREE T)) (offset 16)
>  DB-POSTMODERN::BT         : #<DB-POSTMODERN::PM-INDEXED-BTREE db-table:schemas 2138F01B>
>  DB-POSTMODERN::INDEX-NAME : ELEPHANT::BY-NAME
>  CLOS::.ISL.               : :DONT-KNOW
> 
> Call to (METHOD ELEPHANT::ENSURE-INDEX (INDEXED-BTREE T)) (offset 27)
> 
> Call to (SUBFUNCTION 2 (METHOD ELEPHANT::OPEN-CONTROLLER :AFTER (STORE-CONTROLLER))) (offset 65)
> 
> Call to DB-POSTMODERN::EXECUTE-TRANSACTION-ONE-TRY (offset 169)
>  DB-POSTMODERN::SC                : #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
>  DB-POSTMODERN::TXN-FN            : #<Closure ((METHOD ELEPHANT::OPEN-CONTROLLER :AFTER (STORE-CONTROLLER)) . 2) 21378012>
>  DB-POSTMODERN::ALWAYS-ROLLBACK   : NIL
>  DB-POSTMODERN::TRAN              : #<POSTMODERN::TRANSACTION-HANDLE 21382FE3>
>  DB-POSTMODERN::COMMITED          : NIL
>  DB-POSTMODERN::*TXN-VALUE-CACHE* : NIL
> 
> Call to (METHOD ELEPHANT::EXECUTE-TRANSACTION (DB-POSTMODERN::POSTMODERN-STORE-CONTROLLER T)) (offset 889)
>  DB-POSTMODERN::SC               : #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
>  DB-POSTMODERN::TXN-FN           : #<Closure ((METHOD ELEPHANT::OPEN-CONTROLLER :AFTER (STORE-CONTROLLER)) . 2) 21378012>
>  DBG::G                          : :DONT-KNOW
>  DB-POSTMODERN::ALWAYS-ROLLBACK  : NIL
>  DB-POSTMODERN::RETRY-CLEANUP-FN : NIL
>  DB-POSTMODERN::RETRIES          : 200
>  CLOS::.ISL.                     : :DONT-KNOW
>  POSTMODERN:*DATABASE*           : #<CL-POSTGRES:DATABASE-CONNECTION 2134C41F>
>  DB-POSTMODERN::TRY              : 200
>  DBG::G                          : #<Closure ((METHOD ELEPHANT::EXECUTE-TRANSACTION (DB-POSTMODERN::POSTMODERN-STORE-CONTROLLER T)) . 5) 2137802A>
>  DBG::G                          : #<Function ((METHOD ELEPHANT::EXECUTE-TRANSACTION (DB-POSTMODERN::POSTMODERN-STORE-CONTROLLER T)) . 4) 213026A2>
>  DBG::G                          : #<Closure ((METHOD ELEPHANT::EXECUTE-TRANSACTION (DB-POSTMODERN::POSTMODERN-STORE-CONTROLLER T)) . 3) 21378042>
>  CONDITIONS::*RESTART-CLUSTERS*  : ((#<RESTART ABORT 218FD567>) (#<RESTART ABORT 218FD7CF>) (#<RESTART DB-POSTMODERN::RETRY-TRANSACTION 21345197> #<RESTART DB-POSTMODERN::ABORT-TRANSACTION 213451BB>) (#<RESTART ABORT 213451DF>) (#<RESTART ABORT 21B1398B>))
>  DBG::G                          : #<Function ((METHOD ELEPHANT::EXECUTE-TRANSACTION (DB-POSTMODERN::POSTMODERN-STORE-CONTROLLER T)) . 8) 2130275A>
>  CONDITIONS::*HANDLER-CLUSTERS*  : (((CL-POSTGRES:DATABASE-ERROR . #<Function # 2130275A>)) ((WARNING . EDITOR::EDITOR-EVALUATION-WARNING)) ((END-OF-FILE . #<Closure # 2135380A>) (READER-ERROR . #<Closure # 218FEA32>)))
> 
> Call to CLOS::METHOD-COMBINATION-TEMPLATE (offset 146)
> 
> Call to CLOS::NEXT-METHOD-CALL-2 (offset 87)
>  CONS               : (METHOD ELEPHANT::OPEN-CONTROLLER :AROUND (DB-POSTMODERN::POSTMODERN-STORE-CONTROLLER))
>  CLOS::NEXT-METHODS : (#<Closure CLOS::METHOD-COMBINATION-TEMPLATE 2133B46A>)
>  #:G174431          : #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
>  #:G174432          : NIL
> 
> Call to (METHOD ELEPHANT::OPEN-CONTROLLER :AROUND (DB-POSTMODERN::POSTMODERN-STORE-CONTROLLER)) (offset 61)
>  DB-POSTMODERN::SC          : #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
>  DBG::G                     : NIL
>  CLOS::.ISL.                : :DONT-KNOW
>  DBG::G                     : (#<Closure CLOS::METHOD-COMBINATION-TEMPLATE 2133B46A>)
>  DB-POSTMODERN:*CACHE-MODE* : NIL
> 
> Call to CLOS::METHOD-COMBINATION-TEMPLATE (offset 42)
> 
> Call to OPEN-STORE (offset 66)
> 
> Call to EVAL (offset 113)
>  EXP : (OPEN-STORE *DB-SPEC*)
> 
> Call to EDITOR::EDITOR-EVAL (offset 177)
>  EDITOR:BUFFER  : :DONT-KNOW
>  EDITOR::SEXP   : (OPEN-STORE *DB-SPEC*)
>  EDITOR::ERRORP : T
> 
> ______________________________________________________
> GRATIS f?r alle WEB.DE-Nutzer: Die maxdome Movie-FLAT!
> Jetzt freischalten unter http://movieflat.web.de
> 
> 
> _______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel




From plamen.usenet at gmail.com  Tue Jan  5 15:53:18 2010
From: plamen.usenet at gmail.com (Plamen .)
Date: Tue, 5 Jan 2010 16:53:18 +0100
Subject: [elephant-devel] Problem with LWW 5.1.2, BDB-backend
In-Reply-To: <E8CB270B-0E34-407A-9E7A-B7F34294C888@media.mit.edu>
References: <fd5f17a40912050528i330934dq4257077aac9cc7e0@mail.gmail.com>
	<EA6F6249-6EC2-406D-99E2-D4BA0E79F8B0@media.mit.edu>
	<42c0ab790912071034r29b0ad99i47d904bf07142ffe@mail.gmail.com>
	<fd5f17a40912071346i50020543ia8c71d2fcb2508@mail.gmail.com>
	<558B1CF0-765E-4A9E-919B-B1E14DB51082@media.mit.edu>
	<fd5f17a40912080016s47dff132t9f5024ef7fa02942@mail.gmail.com>
	<42c0ab790912081217l3e1564e7j46a23de8606e8348@mail.gmail.com>
	<732DB9FF-D58B-49EF-8A49-5D54D6CBCD17@media.mit.edu>
	<42c0ab790912081314x65cd38a9nbce2d11d472ab1ae@mail.gmail.com>
	<E8CB270B-0E34-407A-9E7A-B7F34294C888@media.mit.edu>
Message-ID: <fd5f17a41001050753l2f54c550kd1a05082b9101362@mail.gmail.com>

Hello Ian, Elliott,

I haven't much more time over the Chrismass days, but whatI have seen
so far is :

Btw - the problem with Elephant/BDB on LWW is not really an Elephant
one - if compiling under cygwin - there is a clash between the cygwin
and bdb definition of ssize_t, they have different sizes, Bu if
commented out from the bdb db.h, then we get the strange errors
because the pointers in the function table of the ENV struct get
displaced and wrong functions get called. Under VC++ the problem with
the function addresses does not exist, but there I get other also non
Elephant-related problems. Now I'll have again some time to
investigate the issue further.

Regards
Plamen



On Tue, Dec 8, 2009 at 10:35 PM, Ian Eslick <eslick at media.mit.edu> wrote:
> I don't think BDB 4.7 has been tested on windows until now. ?I'm surprised
> 4.5 works with the latest head - but it's probably because you aren't
> exercising some of the 4.7 features Leslie added.
> On Dec 8, 2009, at 1:14 PM, Elliott Slaughter wrote:
>
> On Tue, Dec 8, 2009 at 12:19 PM, Ian Eslick <eslick at media.mit.edu> wrote:
>>
>> Elliott - these DLLs work on your system w/ Lispworks? ?Is everything
>> working for you? ?I just want to make sure we have a baseline.
>
> I went back to my Windows XP build, which I know worked once upon a time,
> and updated to the newest Elephant. With BDB 4.5 and 4.7 installed
> side-by-side, I configured Elephant to use 4.5: the build worked fine. I
> reconfigured for 4.7, and the build broke with error 22. Back to 4.5: build
> works fine. Back again to 4.7: still broken.
> Has Elephant ever been tested against BDB 4.7 on Windows?
> At any rate, I can supply dlls which I know work for BDB 4.5 (attached).
> They work with the newest version of Elephant.
> By the way, line 65 of ele-bdb.asd is hard coded to "-ldb45". That probably
> needs to change. (But it doesn't solve our bug; I already fixed it local and
> it didn't help.)
> Hope that helps?
> --
> Elliott Slaughter
>
> "Don't worry about what anybody else is going to do. The best way to predict
> the future is to invent it." - Alan Kay
> <elephant-1.0-windows-bdb45.7z>_______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel
>
> _______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel
>



From plamen.usenet at gmail.com  Tue Jan  5 15:49:55 2010
From: plamen.usenet at gmail.com (Plamen .)
Date: Tue, 5 Jan 2010 16:49:55 +0100
Subject: [elephant-devel] upgrade from 0.9 to 1.0
In-Reply-To: <412DD00C-B9A5-44E5-9354-CB66CBFB4B4F@media.mit.edu>
References: <2098983249@web.de>
	<412DD00C-B9A5-44E5-9354-CB66CBFB4B4F@media.mit.edu>
Message-ID: <fd5f17a41001050749k31347fe6j7c1ab35ef11d7180@mail.gmail.com>

Hello Frank, if you get Elephant & BDB running under LWW, I would be
interested in the result - see the LispWorks/Berkley post from last
month for details.

Regards
Plamen

On Sun, Jan 3, 2010 at 11:36 PM, Ian Eslick <eslick at media.mit.edu> wrote:
> Hi Frank,
>
> Have you tested with BDB? ?I'm curious if it's a backend issue (the serialized byte-stream seems to be at fault; it's what's causing the condition to be asserted which itself fails).
>
> The other sanity check is to confirming no stale fasls and appropriate settings in my-config.sexp
>
> I can probably take a look at this in depth this coming weekend, but I'm probably too busy this week.
>
> Thank you,
> Ian
>
> On Jan 3, 2010, at 4:51 AM, Frank Schorr wrote:
>
>> Hi Ian:
>>
>> I'm currently revising my software and thought I should also upgrade my elephant from 0.9 to 1.0
>> using lispworks on win32.
>>
>> Compiling was easy, apart from two problems related to base-string:
>>
>> Error: BASE-STRING is not the name of a class
>> when compiling walk-heap in in elephant-1.0/src/elephant/gc.lisp
>> I commented out the method for base-string
>>
>> Error while reading: Saw character U+0080 with syntax type invalid.
>> when compiling ?deftest base-strings in elephant-1.0/tests/testserializer.lisp
>> I commented out the deftest form
>>
>> But calling open-store on a fresh postgres database does not work.
>>
>> I removed the handler-case in (defun deserialize ... in serializer.lisp to let the debuger go down and compiled serializer2.lisp with (debug 3) to produce the backtrace below.
>> There seems to be one issue with the initarg for the condition.
>> But the problem is that error is called at the t clause of the big cond, and I have no idea how to track this down any further .
>>
>> What can I do to improve elephant 1.0 for Lispworks/win ?
>>
>> Best regards
>> Frank
>>
>>
>>
>>
>> Error: The error 'MAKE-INSTANCE is called with keyword :TAG among the arguments (ELEPHANT-TYPE-DESERIALIZATION-ERROR :TAG 0) which is not one of (:CONDITION ELEPHANT::TYPE-TAG).'
>> was raised while coercing (ELEPHANT-TYPE-DESERIALIZATION-ERROR :TAG 0) to a condition.
>> ?1 (continue) retry db-postmodern transaction
>> ?2 DB-POSTMODERN::ABORT-TRANSACTION
>> ?3 (abort) Abort job 5 :(BIND-STANDARD-STREAMS-AND-EXECUTE #<EDITOR::EDITOR-OUTPUT-STREAM #<EDITOR:BUFFER Background Output> 21863E3F> (FUNCALL-BACKGROUND-JOB-AUX #<CAPI:EDITOR-PANE CAPI:EDITOR-PANE ?21AF8C8B> BACKGROUND-REGION-EVAL (# # # # T NIL NIL)))
>>
>> Type :b for backtrace, :c <option number> to proceed, ?or :? for other options
>>
>> CL-USER 1 : 1 > :b :verbose
>> Call to (SUBFUNCTION (LABELS ELEPHANT-SERIALIZER2::%DESERIALIZE) ELEPHANT-SERIALIZER2::DESERIALIZE) (offset 2164)
>> ?ELEPHANT-SERIALIZER2::BS ? ? ? ? ? ? ? ? ? : #S(ELEPHANT-MEMUTIL:BUFFER-STREAM :BUFFER #<Pointer to type (:UNSIGNED :CHAR) = #x0039FFB0> :SIZE 45 :POSITION 2844 :LENGTH 80)
>> ?ELEPHANT-SERIALIZER2::BS ? ? ? ? ? ? ? ? ? : #S(ELEPHANT-MEMUTIL:BUFFER-STREAM :BUFFER #<Pointer to type (:UNSIGNED :CHAR) = #x0039FFB0> :SIZE 45 :POSITION 2844 :LENGTH 80)
>> ?ELEPHANT-SERIALIZER2::TAG ? ? ? ? ? ? ? ? ?: 17
>> ?ELEPHANT-SERIALIZER2::ID ? ? ? ? ? ? ? ? ? : 0
>> ?ELEPHANT-SERIALIZER2::MAYBE-HASH ? ? ? ? ? : NIL
>> ?DBG::|internal-flet-name-for-LOOKUP-ID| ? ?: #<Closure (ELEPHANT-SERIALIZER2::DESERIALIZE LABELS ELEPHANT-SERIALIZER2::LOOKUP-ID) 218FE0FA>
>> ?DBG::|internal-flet-name-for-ADD-OBJECT| ? : #<Closure (ELEPHANT-SERIALIZER2::DESERIALIZE LABELS ELEPHANT-SERIALIZER2::ADD-OBJECT) 218FE112>
>> ?DBG::|internal-flet-name-for-%DESERIALIZE| : #<Closure (ELEPHANT-SERIALIZER2::DESERIALIZE LABELS ELEPHANT-SERIALIZER2::%DESERIALIZE) 218FE0CA>
>> ?ELEPHANT-SERIALIZER2::SC ? ? ? ? ? ? ? ? ? : #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
>> ?ELEPHANT-SERIALIZER2::OID-ONLY ? ? ? ? ? ? : NIL
>>
>> Call to ELEPHANT-SERIALIZER2::DESERIALIZE (offset 375)
>> ?ELEPHANT-SERIALIZER2::BUF-STR ? ? ? ? ? ? ?: #S(ELEPHANT-MEMUTIL:BUFFER-STREAM :BUFFER #<Pointer to type (:UNSIGNED :CHAR) = #x0039FFB0> :SIZE 45 :POSITION 2844 :LENGTH 80)
>> ?ELEPHANT-SERIALIZER2::SC ? ? ? ? ? ? ? ? ? : #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
>> ?ELEPHANT-SERIALIZER2::OID-ONLY ? ? ? ? ? ? : NIL
>> ?DBG::OID-ONLY ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?: T
>> ?ELEPHANT-SERIALIZER2::BUF-STR ? ? ? ? ? ? ?: #S(ELEPHANT-MEMUTIL:BUFFER-STREAM :BUFFER #<Pointer to type (:UNSIGNED :CHAR) = #x0039FFB0> :SIZE 45 :POSITION 2844 :LENGTH 80)
>> ?ELEPHANT-SERIALIZER2::OID-ONLY ? ? ? ? ? ? : NIL
>> ?ELEPHANT-SERIALIZER2::CIRCULARITY-VECTOR ? : #()
>> ?DBG::|internal-flet-name-for-%DESERIALIZE| : #<Closure (ELEPHANT-SERIALIZER2::DESERIALIZE LABELS ELEPHANT-SERIALIZER2::%DESERIALIZE) 218FE0CA>
>> ?DBG::|internal-flet-name-for-ADD-OBJECT| ? : #<Closure (ELEPHANT-SERIALIZER2::DESERIALIZE LABELS ELEPHANT-SERIALIZER2::ADD-OBJECT) 218FE112>
>> ?DBG::|internal-flet-name-for-LOOKUP-ID| ? ?: #<Closure (ELEPHANT-SERIALIZER2::DESERIALIZE LABELS ELEPHANT-SERIALIZER2::LOOKUP-ID) 218FE0FA>
>>
>> Call to DB-POSTMODERN::DESERIALIZE-FROM-DATABASE (offset 63)
>> ?DB-POSTMODERN::X ? ? ? ? : #(17 0 0 0 0 13 9 3 0 0 0 69 81 76 9 11 0 0 0 67 79 77 77 79 78 45 76 73 83 80 4 0 0 0 64 4 0 0 128 63 ...)
>> ?DB-POSTMODERN::SC ? ? ? ?: #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
>> ?DB-POSTMODERN::OIDS-ONLY : NIL
>> ?DB-POSTMODERN::OTHER ? ? : #S(ELEPHANT-MEMUTIL:BUFFER-STREAM :BUFFER #<Pointer to type (:UNSIGNED :CHAR) = #x0039FFB0> :SIZE 45 :POSITION 2844 :LENGTH 80)
>>
>> Call to (METHOD DB-POSTMODERN::INTERNAL-GET-VALUE (T DB-POSTMODERN::PM-BTREE)) (offset 369)
>> ?DB-POSTMODERN::KEY ? ? ? ? ?: "3 INDICES"
>> ?DB-POSTMODERN::BT ? ? ? ? ? : #<DB-POSTMODERN::PM-BTREE db-table:slots 2133F92F>
>> ?CLOS::.ISL. ? ? ? ? ? ? ? ? : :DONT-KNOW
>> ?DB-POSTMODERN::VALUE ? ? ? ?: NIL
>> ?DB-POSTMODERN::EXISTS-P ? ? : NIL
>> ?DB-POSTMODERN::*SC* ? ? ? ? : #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
>> ?DB-POSTMODERN::*CONNECTION* : #<CL-POSTGRES:DATABASE-CONNECTION 2134C41F>
>> ?DB-POSTMODERN::RESULT ? ? ? : #(17 0 0 0 0 13 9 3 0 0 0 69 81 76 9 11 0 0 0 67 79 77 77 79 78 45 76 73 83 80 4 0 0 0 64 4 0 0 128 63 ...)
>>
>> Call to (METHOD GET-VALUE (T DB-POSTMODERN::PM-BTREE)) (offset 20)
>> ?DB-POSTMODERN::KEY : "3 INDICES"
>> ?DB-POSTMODERN::BT ?: #<DB-POSTMODERN::PM-BTREE db-table:slots 2133F92F>
>> ?CLOS::.ISL. ? ? ? ?: :DONT-KNOW
>>
>> Call to (METHOD ELEPHANT::PERSISTENT-SLOT-READER (DB-POSTMODERN::POSTMODERN-STORE-CONTROLLER T T)) (offset 78)
>> ?DB-POSTMODERN::SC ? ? ? ?: #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
>> ?DB-POSTMODERN::INSTANCE ?: #<DB-POSTMODERN::PM-INDEXED-BTREE db-table:schemas 2138F01B>
>> ?DB-POSTMODERN::NAME ? ? ?: DB-POSTMODERN::INDICES
>> ?DB-POSTMODERN::OIDS-ONLY : :DONT-KNOW
>> ?CLOS::.ISL. ? ? ? ? ? ? ?: :DONT-KNOW
>> ?DB-POSTMODERN::*SC* ? ? ?: #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
>>
>> Call to CLOS::METHOD-COMBINATION-TEMPLATE (offset 45)
>>
>> Call to (METHOD CLOS::DYNAMIC-SLOT-VALUE-USING-SLOTD (T T)) (offset 120)
>> ?CLOS::INSTANCE : #<DB-POSTMODERN::PM-INDEXED-BTREE db-table:schemas 2138F01B>
>> ?CLOS::SLOTD ? ?: #<ELEPHANT::PERSISTENT-EFFECTIVE-SLOT-DEFINITION DB-POSTMODERN::INDICES 21369C9B>
>>
>> Call to (METHOD GET-INDEX (DB-POSTMODERN::PM-INDEXED-BTREE T)) (offset 16)
>> ?DB-POSTMODERN::BT ? ? ? ? : #<DB-POSTMODERN::PM-INDEXED-BTREE db-table:schemas 2138F01B>
>> ?DB-POSTMODERN::INDEX-NAME : ELEPHANT::BY-NAME
>> ?CLOS::.ISL. ? ? ? ? ? ? ? : :DONT-KNOW
>>
>> Call to (METHOD ELEPHANT::ENSURE-INDEX (INDEXED-BTREE T)) (offset 27)
>>
>> Call to (SUBFUNCTION 2 (METHOD ELEPHANT::OPEN-CONTROLLER :AFTER (STORE-CONTROLLER))) (offset 65)
>>
>> Call to DB-POSTMODERN::EXECUTE-TRANSACTION-ONE-TRY (offset 169)
>> ?DB-POSTMODERN::SC ? ? ? ? ? ? ? ?: #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
>> ?DB-POSTMODERN::TXN-FN ? ? ? ? ? ?: #<Closure ((METHOD ELEPHANT::OPEN-CONTROLLER :AFTER (STORE-CONTROLLER)) . 2) 21378012>
>> ?DB-POSTMODERN::ALWAYS-ROLLBACK ? : NIL
>> ?DB-POSTMODERN::TRAN ? ? ? ? ? ? ?: #<POSTMODERN::TRANSACTION-HANDLE 21382FE3>
>> ?DB-POSTMODERN::COMMITED ? ? ? ? ?: NIL
>> ?DB-POSTMODERN::*TXN-VALUE-CACHE* : NIL
>>
>> Call to (METHOD ELEPHANT::EXECUTE-TRANSACTION (DB-POSTMODERN::POSTMODERN-STORE-CONTROLLER T)) (offset 889)
>> ?DB-POSTMODERN::SC ? ? ? ? ? ? ? : #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
>> ?DB-POSTMODERN::TXN-FN ? ? ? ? ? : #<Closure ((METHOD ELEPHANT::OPEN-CONTROLLER :AFTER (STORE-CONTROLLER)) . 2) 21378012>
>> ?DBG::G ? ? ? ? ? ? ? ? ? ? ? ? ?: :DONT-KNOW
>> ?DB-POSTMODERN::ALWAYS-ROLLBACK ?: NIL
>> ?DB-POSTMODERN::RETRY-CLEANUP-FN : NIL
>> ?DB-POSTMODERN::RETRIES ? ? ? ? ?: 200
>> ?CLOS::.ISL. ? ? ? ? ? ? ? ? ? ? : :DONT-KNOW
>> ?POSTMODERN:*DATABASE* ? ? ? ? ? : #<CL-POSTGRES:DATABASE-CONNECTION 2134C41F>
>> ?DB-POSTMODERN::TRY ? ? ? ? ? ? ?: 200
>> ?DBG::G ? ? ? ? ? ? ? ? ? ? ? ? ?: #<Closure ((METHOD ELEPHANT::EXECUTE-TRANSACTION (DB-POSTMODERN::POSTMODERN-STORE-CONTROLLER T)) . 5) 2137802A>
>> ?DBG::G ? ? ? ? ? ? ? ? ? ? ? ? ?: #<Function ((METHOD ELEPHANT::EXECUTE-TRANSACTION (DB-POSTMODERN::POSTMODERN-STORE-CONTROLLER T)) . 4) 213026A2>
>> ?DBG::G ? ? ? ? ? ? ? ? ? ? ? ? ?: #<Closure ((METHOD ELEPHANT::EXECUTE-TRANSACTION (DB-POSTMODERN::POSTMODERN-STORE-CONTROLLER T)) . 3) 21378042>
>> ?CONDITIONS::*RESTART-CLUSTERS* ?: ((#<RESTART ABORT 218FD567>) (#<RESTART ABORT 218FD7CF>) (#<RESTART DB-POSTMODERN::RETRY-TRANSACTION 21345197> #<RESTART DB-POSTMODERN::ABORT-TRANSACTION 213451BB>) (#<RESTART ABORT 213451DF>) (#<RESTART ABORT 21B1398B>))
>> ?DBG::G ? ? ? ? ? ? ? ? ? ? ? ? ?: #<Function ((METHOD ELEPHANT::EXECUTE-TRANSACTION (DB-POSTMODERN::POSTMODERN-STORE-CONTROLLER T)) . 8) 2130275A>
>> ?CONDITIONS::*HANDLER-CLUSTERS* ?: (((CL-POSTGRES:DATABASE-ERROR . #<Function # 2130275A>)) ((WARNING . EDITOR::EDITOR-EVALUATION-WARNING)) ((END-OF-FILE . #<Closure # 2135380A>) (READER-ERROR . #<Closure # 218FEA32>)))
>>
>> Call to CLOS::METHOD-COMBINATION-TEMPLATE (offset 146)
>>
>> Call to CLOS::NEXT-METHOD-CALL-2 (offset 87)
>> ?CONS ? ? ? ? ? ? ? : (METHOD ELEPHANT::OPEN-CONTROLLER :AROUND (DB-POSTMODERN::POSTMODERN-STORE-CONTROLLER))
>> ?CLOS::NEXT-METHODS : (#<Closure CLOS::METHOD-COMBINATION-TEMPLATE 2133B46A>)
>> ?#:G174431 ? ? ? ? ?: #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
>> ?#:G174432 ? ? ? ? ?: NIL
>>
>> Call to (METHOD ELEPHANT::OPEN-CONTROLLER :AROUND (DB-POSTMODERN::POSTMODERN-STORE-CONTROLLER)) (offset 61)
>> ?DB-POSTMODERN::SC ? ? ? ? ?: #<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 testdb postgres %postgres%)>
>> ?DBG::G ? ? ? ? ? ? ? ? ? ? : NIL
>> ?CLOS::.ISL. ? ? ? ? ? ? ? ?: :DONT-KNOW
>> ?DBG::G ? ? ? ? ? ? ? ? ? ? : (#<Closure CLOS::METHOD-COMBINATION-TEMPLATE 2133B46A>)
>> ?DB-POSTMODERN:*CACHE-MODE* : NIL
>>
>> Call to CLOS::METHOD-COMBINATION-TEMPLATE (offset 42)
>>
>> Call to OPEN-STORE (offset 66)
>>
>> Call to EVAL (offset 113)
>> ?EXP : (OPEN-STORE *DB-SPEC*)
>>
>> Call to EDITOR::EDITOR-EVAL (offset 177)
>> ?EDITOR:BUFFER ?: :DONT-KNOW
>> ?EDITOR::SEXP ? : (OPEN-STORE *DB-SPEC*)
>> ?EDITOR::ERRORP : T
>>
>> ______________________________________________________
>> GRATIS f?r alle WEB.DE-Nutzer: Die maxdome Movie-FLAT!
>> Jetzt freischalten unter http://movieflat.web.de
>>
>>
>> _______________________________________________
>> elephant-devel site list
>> elephant-devel at common-lisp.net
>> http://common-lisp.net/mailman/listinfo/elephant-devel
>
>
> _______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel
>



From franks-muc at web.de  Wed Jan  6 09:27:00 2010
From: franks-muc at web.de (Frank Schorr)
Date: Wed, 06 Jan 2010 10:27:00 +0100
Subject: [elephant-devel] upgrade from 0.9 to 1.0
Message-ID: <3247065@web.de>

Hi Ian,

thank you for your response.

I can exclude a stale fasl problem. 

This is my-config.sexp:
((:compiler . :cygwin)
 (:berkeley-db-version . "4.7")
 (:berkeley-db-include-dir . "C:/Programme/Oracle/Berkeley DB 4.7.25/include/")
 (:berkeley-db-lib-dir . "C:/Programme/Oracle/Berkeley DB 4.7.25/lib/")
 (:berkeley-db-lib . "C:/Programme/Oracle/Berkeley DB 4.7.25/bin/libdb47.dll")
 (:berkeley-db-deadlock . "C:/Programme/Oracle/Berkeley DB 4.7.25/bin/db_deadlock.exe")
 (:berkeley-db-cachesize . 20971520)
 (:berkeley-db-max-locks . 2000)
 (:berkeley-db-max-objects . 2000)
 (:berkeley-db-map-degree2 . t)
 (:berkeley-db-mvcc . nil)
 (:clsql-lib-paths . nil)
 (:prebuilt-libraries . nil))

I tried to install ele-bdb.
While memutil.dll is generated by asdf, libberkeley-db.dll is not.
I undestand that 4.7 is the current BDB version.

There is still a conflict in a definition of ssize_t with one of cygwin's include files (see http://thread.gmane.org/gmane.lisp.elephant.devel/271 ) 
This time I deleted the definition of ssize_t from BDB's db.h and db-bdb\libberkeley-db.c is compiled with

$ gcc -L'/cygdrive/C/Programme/Oracle/Berkeley DB 4.7.25/lib/' -I'/cygdrive/C/Programme/O
racle/Berkeley DB 4.7.25/include/' -llibdb47 -mno-cygwin -mwindows -Wall -c -std=c99 "c:\
lisp\libraries\elephant-1.0\src\db-bdb\libberkeley-db.c"

Some warnings: 

c:\lisp\libraries\elephant-1.0\src\db-bdb\libberkeley-db.c: In function `lisp_compare2':
c:\lisp\libraries\elephant-1.0\src\db-bdb\libberkeley-db.c:1053: warning: unused variable
`i'
c:\lisp\libraries\elephant-1.0\src\db-bdb\libberkeley-db.c: In function `lisp_compare_key2
':
c:\lisp\libraries\elephant-1.0\src\db-bdb\libberkeley-db.c:1147: warning: unused variable
`i'
c:\lisp\libraries\elephant-1.0\src\db-bdb\libberkeley-db.c: In function `case_cmp':
c:\lisp\libraries\elephant-1.0\src\db-bdb\libberkeley-db.c:1306: warning: implicit declara
tion of function `_strnicmp'


$ dlltool -z "c:\lisp\libraries\elephant-1.0\src\db-bdb\libberkeley-db.def" --export-all-
symbols -e exports.o -l "c:\lisp\libraries\elephant-1.0\src\db-bdb\libberkeley-db.lib" "c
:\lisp\libraries\elephant-1.0\src\db-bdb\libberkeley-db.o"

$ gcc -L'/cygdrive/C/Programme/Oracle/Berkeley DB 4.7.25/lib/' -I'/cygdrive/C/Programme/O
racle/Berkeley DB 4.7.25/include/' -llibdb47 -shared -mno-cygwin -mwindows -Wall "c:\lisp
\libraries\elephant-1.0\src\db-bdb\libberkeley-db.o" exports.o -o "c:\lisp\libraries\elep
hant-1.0\src\db-bdb\libberkeley-db.dll"

c:\lisp\libraries\elephant-1.0\src\db-bdb\libberkeley-db.o:libberkeley-db.c:(.text+0x2ba):
 undefined reference to `_db_env_create'
c:\lisp\libraries\elephant-1.0\src\db-bdb\libberkeley-db.o:libberkeley-db.c:(.text+0x2d7):
 undefined reference to `_db_strerror'
c:\lisp\libraries\elephant-1.0\src\db-bdb\libberkeley-db.o:libberkeley-db.c:(.text+0x489):
 undefined reference to `_db_create'
c:\lisp\libraries\elephant-1.0\src\db-bdb\libberkeley-db.o:libberkeley-db.c:(.text+0xe88):
 undefined reference to `_db_sequence_create'
collect2: ld returned 1 exit status

I hope this can help ?

Best regards,
Frank



> -----Urspr?ngliche Nachricht-----
> Von: "Ian Eslick" <eslick at media.mit.edu>
> Gesendet: 03.01.10 23:36:54
> An: Elephant bugs and development <elephant-devel at common-lisp.net>
> Betreff: Re: [elephant-devel] upgrade from 0.9 to 1.0
> Priorit?t: Niedrig


> Hi Frank,
> 
> Have you tested with BDB?  I'm curious if it's a backend issue (the serialized byte-stream seems to be at fault; it's what's causing the condition to be asserted which itself fails).  
> 
> The other sanity check is to confirming no stale fasls and appropriate settings in my-config.sexp
> 
> I can probably take a look at this in depth this coming weekend, but I'm probably too busy this week.
> 
> Thank you,
> Ian
> 

___________________________________________________________
Preisknaller: WEB.DE DSL Flatrate f?r nur 16,99 Euro/mtl.! 
http://produkte.web.de/go/02/




From franks-muc at web.de  Wed Jan  6 09:36:08 2010
From: franks-muc at web.de (Frank Schorr)
Date: Wed, 06 Jan 2010 10:36:08 +0100
Subject: [elephant-devel] upgrade from 0.9 to 1.0
Message-ID: <3249935@web.de>

Hi Plamen,
I had BDB running in one of the earlier versions of elephant. 
You should be aware that BDB blocks under LW/win if multiple threads access the db.
That is why I am using the postmodern backend. It is simple, stable and I don't have to care about performance.
Still, I will try to get BDB up again and let you know.
Best regards,
Frank


> -----Urspr?ngliche Nachricht-----
> Von: "Plamen ." <plamen.usenet at gmail.com>
> Gesendet: 05.01.10 16:56:55
> An: Elephant bugs and development <elephant-devel at common-lisp.net>
> Betreff: Re: [elephant-devel] upgrade from 0.9 to 1.0


> Hello Frank, if you get Elephant & BDB running under LWW, I would be
> interested in the result - see the LispWorks/Berkley post from last
> month for details.
> 
> Regards
> Plamen
> 

___________________________________________________________
Preisknaller: WEB.DE DSL Flatrate f?r nur 16,99 Euro/mtl.! 
http://produkte.web.de/go/02/




From reddaly at gmail.com  Thu Jan  7 05:33:49 2010
From: reddaly at gmail.com (Red Daly)
Date: Wed, 6 Jan 2010 21:33:49 -0800
Subject: [elephant-devel] Class indexes dropped after database restart?
In-Reply-To: <728193FF-D057-4D47-9DFA-CCC3C4185F24@media.mit.edu>
References: <f6700f0c0909222008p37b9e3e6ue541d8f60bf22d10@mail.gmail.com>
	<f6700f0c0909222041j2cc8802cl2b7c8f772f125c5b@mail.gmail.com>
	<EA3284BE-E503-4F4A-8A28-487F3ACB6D5D@media.mit.edu>
	<4566E50F-AEC0-4930-B5C9-E75A4FB2967D@gmail.com>
	<f6700f0c0912291252n18a2a9c8y5d27c2ae3eeb8773@mail.gmail.com>
	<96000188-95CB-4AF5-9E5F-32CCA018B855@media.mit.edu>
	<f6700f0c0912292142y73f9b97nbcb1fde1a6138b5d@mail.gmail.com>
	<728193FF-D057-4D47-9DFA-CCC3C4185F24@media.mit.edu>
Message-ID: <f6700f0c1001062133n2ac51853r57c78b231c360275@mail.gmail.com>

I'm just checking in to see if anyone has been able to reproduce this
bug.  It's a pretty nasty one and my solution does not scale
well--requires a lot of time when reopening a database to construct
the indexes.

-Red

On Tue, Dec 29, 2009 at 9:51 PM, Ian Eslick <eslick at media.mit.edu> wrote:
> I'll give it a try with that configuration...
>
> Thanks,
> Ian
>
> On Dec 29, 2009, at 9:42 PM, Red Daly wrote:
>
>> On Tue, Dec 29, 2009 at 5:53 PM, Ian Eslick <eslick at media.mit.edu> wrote:
>>> Hmmm....I can't reproduce this locally with my copy of latest.
>>>
>>> Your test code passes on a fresh DB as well. ?It's possible you're catching an error having to do with opening non 1.0 databases.
>>>
>>> A few quick sanity checks:
>>> 1) Did you clean out the test repository before running? ? (tests/delscript.sh)
>>> 2) Also, are you using elephant-1.0 or the defunct elephant-dev darcs repository?
>>
>>
>> I ran the test in a different, non-elephant directory with a fresh
>> darcs repository pulled from the elephant-1.0 tree. ?Here's a copy of
>> the my-config.sexp:
>>
>> ((:compiler . :gcc)
>> (:berkeley-db-version . "4.7")
>> (:berkeley-db-include-dir . "/usr/local/BerkeleyDB.4.7/include/")
>> (:berkeley-db-lib-dir . "/usr/local/BerkeleyDB.4.7/lib/")
>> (:berkeley-db-lib . "/usr/local/BerkeleyDB.4.7/lib/libdb-4.7.so")
>> (:berkeley-db-deadlock . "/usr/local/BerkeleyDB.4.7/bin/db_deadlock")
>> (:berkeley-db-cachesize . 20971520)
>> (:berkeley-db-max-locks . 2000)
>> (:berkeley-db-max-objects . 2000)
>> (:berkeley-db-max-transactions . 1000)
>> (:berkeley-db-map-degree2 . t)
>> (:berkeley-db-mvcc . nil)
>> (:clsql-lib-paths . nil)
>> (:prebuilt-libraries . nil))
>>
>> Did you try to reproduce this using Linux/SBCL? ?I don't know why it
>> would make a difference.
>>
>>>
>>> Thank you,
>>> Ian
>>
>> Best,
>> Red
>>
>>>
>>> On Dec 29, 2009, at 12:52 PM, Red Daly wrote:
>>>
>>>> This bug is easy to reproduce with the latest version of elephant.
>>>> Here is some code I used to reproduce the bug:
>>>>
>>>> (require :elephant)
>>>>
>>>> (defpackage :ele-bug
>>>> ? ?(:use :ele :cl))
>>>>
>>>> (in-package :ele-bug)
>>>>
>>>> (defclass a ()
>>>> ?((x :initarg :x :index t :initform 0 :accessor x))
>>>> ?(:metaclass ele:persistent-metaclass))
>>>>
>>>> (defun create-instances (n &optional (class 'a))
>>>> ?(dotimes (i n)
>>>> ? ?(make-instance class :x i)))
>>>>
>>>> (defun stats ()
>>>> ?(dolist (class-sym '(a b))
>>>> ? ?(format t "~A: ~A instances; ~A with value 10~%"
>>>> ? ? ? ? ? class-sym
>>>> ? ? ? ? ? (length (get-instances-by-class class-sym))
>>>> ? ? ? ? ? (length (get-instances-by-value class-sym 'x 10)))))
>>>>
>>>> (defun open-close-test ()
>>>> ?(declare (optimize (debug 3)))
>>>> ?(macrolet ((is (form)
>>>> ? ? ? ? ? ? ?`(assert ,form)))
>>>> ? ?(flet ((open-it ()
>>>> ? ? ? ? ? ?(ele:open-store '(:bdb "db2/")))
>>>> ? ? ? ? ?(test-class-indexes (n-class n-10)
>>>> ? ? ? ? ? ?(is (= n-class (length (get-instances-by-class 'a))))
>>>> ? ? ? ? ? ?(is (= n-10 ? ?(length (get-instances-by-value 'a 'x 10))))))
>>>> ? ? ?(with-open-store ('(:bdb "db2/"))
>>>> ? ? ? (create-instances 100 'a)
>>>> ? ? ? (test-class-indexes 100 1))
>>>> ? ? ?(with-open-store ('(:bdb "db2/"))
>>>> ? ? ? (test-class-indexes 100 1)))))
>>>>
>>>> (open-close-test)
>>>>
>>>> I was able to fix the problem with a minor patch, but I doubt the
>>>> correctness of my solution. ?Here is the diff:
>>>>
>>>> diff -rN old-elephant-1.0/src/elephant/controller.lisp
>>>> new-elephant-1.0/src/elephant/controller.lisp
>>>> 711c711,712
>>>> < ? ? ? ? ? ? ? ? ? ? ? :key-form 'schema-classname-keyform))
>>>> ---
>>>>> ? ? ? ? ? ? ? ? ? ? ?:key-form 'schema-classname-keyform
>>>>> ? ? ? ? ? ? ? ? ? ? ?:populate t))
>>>> 716c717,718
>>>> < ? ? ? ? ? ? ? ? ? ? ? :key-form 'instance-cidx-keyform))))
>>>> ---
>>>>> ? ? ? ? ? ? ? ? ? ? ?:key-form 'instance-cidx-keyform
>>>>> ? ? ? ? ? ? ? ? ? ? ?:populate t))))
>>>>
>>>>
>>>> I essentially just added a :populate t argument to the open-controller
>>>> method. ?This seems to indicate that the 'BY-NAME secondary indices
>>>> that map a class indices to OIDs, and class names to class indices, do
>>>> not persist. ?Is this expected behavior? ?I'm not familiar enough with
>>>> the internals to tell.
>>>>
>>>> Thanks,
>>>> Red
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Wed, Sep 23, 2009 at 3:27 PM, Red Daly <reddaly at gmail.com> wrote:
>>>>> This is the 1.0 repository. ?I will see if I can reproduce the problem in a
>>>>> test case.
>>>>> Red
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Sep 23, 2009, at 9:50 AM, Ian Eslick <eslick at media.mit.edu> wrote:
>>>>>
>>>>> Which darcs repository? ?There is the old 0.91 release and the new
>>>>> elephant-1.0 branch...
>>>>> Ian
>>>>> On Sep 22, 2009, at 8:41 PM, Red Daly wrote:
>>>>>
>>>>> I should also note that I am using the version of elephant from darcs. ?And
>>>>> I discovered that when the program went down it was due to a segfault (I
>>>>> believe in emacs). ?However, all instances had been created under many
>>>>> different transactions that did not abort.
>>>>>
>>>>> Here is some more fiddling around:
>>>>>
>>>>> CL-USER> (lisp-implementation-version)
>>>>> "1.0.29.54.rc1"
>>>>> BOOKS> (ele::get-db-schemas *ele-db* 'material)
>>>>> NIL
>>>>> BOOKS> (ele::controller-instance-class-index *ele-db*)
>>>>> #<BDB-BTREE-INDEX
>>>>> oid:13701>
>>>>> BOOKS> (ele:map-btree #'(lambda (key
>>>>> val)
>>>>> ? ? ? ? ? ? ? ? ? ? ? ? ? (format t "~S => ~S~%" key
>>>>> val))
>>>>> ? ? ? ? ? ? ? ? ? ? ? (ele::controller-instance-class-index *ele-db*))
>>>>> 307 =>
>>>>> 307
>>>>> NIL
>>>>>
>>>>>
>>>>> Red
>>>>>
>>>>> On Tue, Sep 22, 2009 at 8:08 PM, Red Daly <reddaly at gmail.com> wrote:
>>>>>>
>>>>>> I noticed there was a disparity between get-instances-by-class and
>>>>>> map-inverted-index. ?I will let the code speak for itself:
>>>>>>
>>>>>> BOOKS> (length (ele:map-inverted-index #'(lambda (isbn obj) obj) 'material
>>>>>> 'isbn :collect
>>>>>> t))
>>>>>>
>>>>>> 1945
>>>>>> BOOKS> (length (ele:get-instances-by-class 'material))
>>>>>> 0
>>>>>> BOOKS> (defparameter f (make-instance 'material :title "Fake Book"))
>>>>>>
>>>>>> F
>>>>>> BOOKS> (length (ele:get-instances-by-class 'material))
>>>>>>
>>>>>> 1
>>>>>> BOOKS> (length (ele:map-inverted-index #'(lambda (isbn obj) obj) 'material
>>>>>> 'isbn :collect
>>>>>> t))
>>>>>> 1946
>>>>>>
>>>>>> There is a similar problem with the university class.
>>>>>>
>>>>>> BOOKS> (length (ele:get-instances-by-class 'university))
>>>>>> 0
>>>>>> BOOKS> *stanford-university*
>>>>>> #<UNIVERSITY
>>>>>> oid:204>
>>>>>> BOOKS> (official-name *stanford-university*)
>>>>>> "Stanford University"
>>>>>>
>>>>>> All of the instances in the database were created in a prior session.
>>>>>> Then I shut down the DB and restarted Lisp. ?Now MAP-CLASS and
>>>>>> GET-INSTANCES-BY-CLASS return nil for all classes. ?It seems like new
>>>>>> instances get added to the "class index," but older instances are not
>>>>>> found. ?However, these classes persist in the inverted slot indexes. ?Can
>>>>>> anybody diagnose what's going on?
>>>>>>
>>>>>> here are the definitions of the classes:
>>>>>>
>>>>>> (defclass department ()
>>>>>> ? ((university :initarg :university :initform nil :accessor
>>>>>> department-university
>>>>>> ? ? ? ? ? ? ? ?:index t)
>>>>>> ? ?(official-name :initarg :official-name :initform nil :accessor
>>>>>> official-name)
>>>>>> ? ?(common-name :initarg :common-name :initform nil :accessor common-name)
>>>>>> ? ?(abbreviation :initarg :abbreviation :initform nil :accessor
>>>>>> abbreviation
>>>>>> ? ? ? ? ? ? ? ? ?:index t))
>>>>>> ? (:metaclass ele:persistent-metaclass)
>>>>>> ? (:documentation "A department has a bunch of course listings."))
>>>>>>
>>>>>> (defclass material ()
>>>>>> ? ((title :initarg :title :initform nil :accessor material-title
>>>>>> ? ? ? ? ? :index t)
>>>>>> ? ?(authors :initarg :authors :initform nil :accessor material-authors) ;;
>>>>>> a list of
>>>>>> authors
>>>>>> ? ?(edition :initarg :edition :initform nil :accessor material-edition)
>>>>>> ? ?(isbn :initarg :isbn :initform nil :accessor material-isbn
>>>>>> ? ? ? ? ?:index t)
>>>>>> ? ?(asin :initarg :asin :initform nil :accessor material-asin
>>>>>> ? ? ? ? ?:index t
>>>>>> ? ? ? ? ?:documentation "An Amazon.com identifier that uniquely identifies
>>>>>> the material")
>>>>>> ? ?(image-uri :initarg :image-uri :initform nil :accessor
>>>>>> material-image-uri))
>>>>>> ? (:metaclass ele:persistent-metaclass))
>>>>>>
>>>>>> Thanks,
>>>>>> Red
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> elephant-devel site list
>>>>> elephant-devel at common-lisp.net
>>>>> http://common-lisp.net/mailman/listinfo/elephant-devel
>>>>>
>>>>> _______________________________________________
>>>>> elephant-devel site list
>>>>> elephant-devel at common-lisp.net
>>>>> http://common-lisp.net/mailman/listinfo/elephant-devel
>>>>
>>>> _______________________________________________
>>>> elephant-devel site list
>>>> elephant-devel at common-lisp.net
>>>> http://common-lisp.net/mailman/listinfo/elephant-devel
>>>
>>>
>>> _______________________________________________
>>> elephant-devel site list
>>> elephant-devel at common-lisp.net
>>> http://common-lisp.net/mailman/listinfo/elephant-devel
>>>
>>
>> _______________________________________________
>> elephant-devel site list
>> elephant-devel at common-lisp.net
>> http://common-lisp.net/mailman/listinfo/elephant-devel
>
>



From eslick at media.mit.edu  Sun Jan 10 20:31:34 2010
From: eslick at media.mit.edu (Ian Eslick)
Date: Sun, 10 Jan 2010 15:31:34 -0500
Subject: [elephant-devel] Class indexes dropped after database restart?
In-Reply-To: <f6700f0c1001062133n2ac51853r57c78b231c360275@mail.gmail.com>
References: <f6700f0c0909222008p37b9e3e6ue541d8f60bf22d10@mail.gmail.com>
	<f6700f0c0909222041j2cc8802cl2b7c8f772f125c5b@mail.gmail.com>
	<EA3284BE-E503-4F4A-8A28-487F3ACB6D5D@media.mit.edu>
	<4566E50F-AEC0-4930-B5C9-E75A4FB2967D@gmail.com>
	<f6700f0c0912291252n18a2a9c8y5d27c2ae3eeb8773@mail.gmail.com>
	<96000188-95CB-4AF5-9E5F-32CCA018B855@media.mit.edu>
	<f6700f0c0912292142y73f9b97nbcb1fde1a6138b5d@mail.gmail.com>
	<728193FF-D057-4D47-9DFA-CCC3C4185F24@media.mit.edu>
	<f6700f0c1001062133n2ac51853r57c78b231c360275@mail.gmail.com>
Message-ID: <3F9E9447-90BE-4E22-AF1F-3F0015D9CFE7@media.mit.edu>

Hi Red,

I'm sorry this took so long to get to.  I had to bring up a new Linux VM to try to reproduce your test among other things.  Unfortunately I'm unable to reproduce this locally on the latest Ubuntu Linux w/ sbcl 1.0.32, BDB 4.7, and the latest elephant-1.0 tree.

I have some theories about what it could be, but if you still get this on the exact above configuration with a fresh image and database I'm at a bit of a loss.

Ian

On Jan 7, 2010, at 12:33 AM, Red Daly wrote:

> I'm just checking in to see if anyone has been able to reproduce this
> bug.  It's a pretty nasty one and my solution does not scale
> well--requires a lot of time when reopening a database to construct
> the indexes.
> 
> -Red
> 
> On Tue, Dec 29, 2009 at 9:51 PM, Ian Eslick <eslick at media.mit.edu> wrote:
>> I'll give it a try with that configuration...
>> 
>> Thanks,
>> Ian
>> 
>> On Dec 29, 2009, at 9:42 PM, Red Daly wrote:
>> 
>>> On Tue, Dec 29, 2009 at 5:53 PM, Ian Eslick <eslick at media.mit.edu> wrote:
>>>> Hmmm....I can't reproduce this locally with my copy of latest.
>>>> 
>>>> Your test code passes on a fresh DB as well.  It's possible you're catching an error having to do with opening non 1.0 databases.
>>>> 
>>>> A few quick sanity checks:
>>>> 1) Did you clean out the test repository before running?   (tests/delscript.sh)
>>>> 2) Also, are you using elephant-1.0 or the defunct elephant-dev darcs repository?
>>> 
>>> 
>>> I ran the test in a different, non-elephant directory with a fresh
>>> darcs repository pulled from the elephant-1.0 tree.  Here's a copy of
>>> the my-config.sexp:
>>> 
>>> ((:compiler . :gcc)
>>> (:berkeley-db-version . "4.7")
>>> (:berkeley-db-include-dir . "/usr/local/BerkeleyDB.4.7/include/")
>>> (:berkeley-db-lib-dir . "/usr/local/BerkeleyDB.4.7/lib/")
>>> (:berkeley-db-lib . "/usr/local/BerkeleyDB.4.7/lib/libdb-4.7.so")
>>> (:berkeley-db-deadlock . "/usr/local/BerkeleyDB.4.7/bin/db_deadlock")
>>> (:berkeley-db-cachesize . 20971520)
>>> (:berkeley-db-max-locks . 2000)
>>> (:berkeley-db-max-objects . 2000)
>>> (:berkeley-db-max-transactions . 1000)
>>> (:berkeley-db-map-degree2 . t)
>>> (:berkeley-db-mvcc . nil)
>>> (:clsql-lib-paths . nil)
>>> (:prebuilt-libraries . nil))
>>> 
>>> Did you try to reproduce this using Linux/SBCL?  I don't know why it
>>> would make a difference.
>>> 
>>>> 
>>>> Thank you,
>>>> Ian
>>> 
>>> Best,
>>> Red
>>> 
>>>> 
>>>> On Dec 29, 2009, at 12:52 PM, Red Daly wrote:
>>>> 
>>>>> This bug is easy to reproduce with the latest version of elephant.
>>>>> Here is some code I used to reproduce the bug:
>>>>> 
>>>>> (require :elephant)
>>>>> 
>>>>> (defpackage :ele-bug
>>>>>    (:use :ele :cl))
>>>>> 
>>>>> (in-package :ele-bug)
>>>>> 
>>>>> (defclass a ()
>>>>>  ((x :initarg :x :index t :initform 0 :accessor x))
>>>>>  (:metaclass ele:persistent-metaclass))
>>>>> 
>>>>> (defun create-instances (n &optional (class 'a))
>>>>>  (dotimes (i n)
>>>>>    (make-instance class :x i)))
>>>>> 
>>>>> (defun stats ()
>>>>>  (dolist (class-sym '(a b))
>>>>>    (format t "~A: ~A instances; ~A with value 10~%"
>>>>>           class-sym
>>>>>           (length (get-instances-by-class class-sym))
>>>>>           (length (get-instances-by-value class-sym 'x 10)))))
>>>>> 
>>>>> (defun open-close-test ()
>>>>>  (declare (optimize (debug 3)))
>>>>>  (macrolet ((is (form)
>>>>>              `(assert ,form)))
>>>>>    (flet ((open-it ()
>>>>>            (ele:open-store '(:bdb "db2/")))
>>>>>          (test-class-indexes (n-class n-10)
>>>>>            (is (= n-class (length (get-instances-by-class 'a))))
>>>>>            (is (= n-10    (length (get-instances-by-value 'a 'x 10))))))
>>>>>      (with-open-store ('(:bdb "db2/"))
>>>>>       (create-instances 100 'a)
>>>>>       (test-class-indexes 100 1))
>>>>>      (with-open-store ('(:bdb "db2/"))
>>>>>       (test-class-indexes 100 1)))))
>>>>> 
>>>>> (open-close-test)
>>>>> 
>>>>> I was able to fix the problem with a minor patch, but I doubt the
>>>>> correctness of my solution.  Here is the diff:
>>>>> 
>>>>> diff -rN old-elephant-1.0/src/elephant/controller.lisp
>>>>> new-elephant-1.0/src/elephant/controller.lisp
>>>>> 711c711,712
>>>>> <                       :key-form 'schema-classname-keyform))
>>>>> ---
>>>>>>                      :key-form 'schema-classname-keyform
>>>>>>                      :populate t))
>>>>> 716c717,718
>>>>> <                       :key-form 'instance-cidx-keyform))))
>>>>> ---
>>>>>>                      :key-form 'instance-cidx-keyform
>>>>>>                      :populate t))))
>>>>> 
>>>>> 
>>>>> I essentially just added a :populate t argument to the open-controller
>>>>> method.  This seems to indicate that the 'BY-NAME secondary indices
>>>>> that map a class indices to OIDs, and class names to class indices, do
>>>>> not persist.  Is this expected behavior?  I'm not familiar enough with
>>>>> the internals to tell.
>>>>> 
>>>>> Thanks,
>>>>> Red
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> On Wed, Sep 23, 2009 at 3:27 PM, Red Daly <reddaly at gmail.com> wrote:
>>>>>> This is the 1.0 repository.  I will see if I can reproduce the problem in a
>>>>>> test case.
>>>>>> Red
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> On Sep 23, 2009, at 9:50 AM, Ian Eslick <eslick at media.mit.edu> wrote:
>>>>>> 
>>>>>> Which darcs repository?  There is the old 0.91 release and the new
>>>>>> elephant-1.0 branch...
>>>>>> Ian
>>>>>> On Sep 22, 2009, at 8:41 PM, Red Daly wrote:
>>>>>> 
>>>>>> I should also note that I am using the version of elephant from darcs.  And
>>>>>> I discovered that when the program went down it was due to a segfault (I
>>>>>> believe in emacs).  However, all instances had been created under many
>>>>>> different transactions that did not abort.
>>>>>> 
>>>>>> Here is some more fiddling around:
>>>>>> 
>>>>>> CL-USER> (lisp-implementation-version)
>>>>>> "1.0.29.54.rc1"
>>>>>> BOOKS> (ele::get-db-schemas *ele-db* 'material)
>>>>>> NIL
>>>>>> BOOKS> (ele::controller-instance-class-index *ele-db*)
>>>>>> #<BDB-BTREE-INDEX
>>>>>> oid:13701>
>>>>>> BOOKS> (ele:map-btree #'(lambda (key
>>>>>> val)
>>>>>>                           (format t "~S => ~S~%" key
>>>>>> val))
>>>>>>                       (ele::controller-instance-class-index *ele-db*))
>>>>>> 307 =>
>>>>>> 307
>>>>>> NIL
>>>>>> 
>>>>>> 
>>>>>> Red
>>>>>> 
>>>>>> On Tue, Sep 22, 2009 at 8:08 PM, Red Daly <reddaly at gmail.com> wrote:
>>>>>>> 
>>>>>>> I noticed there was a disparity between get-instances-by-class and
>>>>>>> map-inverted-index.  I will let the code speak for itself:
>>>>>>> 
>>>>>>> BOOKS> (length (ele:map-inverted-index #'(lambda (isbn obj) obj) 'material
>>>>>>> 'isbn :collect
>>>>>>> t))
>>>>>>> 
>>>>>>> 1945
>>>>>>> BOOKS> (length (ele:get-instances-by-class 'material))
>>>>>>> 0
>>>>>>> BOOKS> (defparameter f (make-instance 'material :title "Fake Book"))
>>>>>>> 
>>>>>>> F
>>>>>>> BOOKS> (length (ele:get-instances-by-class 'material))
>>>>>>> 
>>>>>>> 1
>>>>>>> BOOKS> (length (ele:map-inverted-index #'(lambda (isbn obj) obj) 'material
>>>>>>> 'isbn :collect
>>>>>>> t))
>>>>>>> 1946
>>>>>>> 
>>>>>>> There is a similar problem with the university class.
>>>>>>> 
>>>>>>> BOOKS> (length (ele:get-instances-by-class 'university))
>>>>>>> 0
>>>>>>> BOOKS> *stanford-university*
>>>>>>> #<UNIVERSITY
>>>>>>> oid:204>
>>>>>>> BOOKS> (official-name *stanford-university*)
>>>>>>> "Stanford University"
>>>>>>> 
>>>>>>> All of the instances in the database were created in a prior session.
>>>>>>> Then I shut down the DB and restarted Lisp.  Now MAP-CLASS and
>>>>>>> GET-INSTANCES-BY-CLASS return nil for all classes.  It seems like new
>>>>>>> instances get added to the "class index," but older instances are not
>>>>>>> found.  However, these classes persist in the inverted slot indexes.  Can
>>>>>>> anybody diagnose what's going on?
>>>>>>> 
>>>>>>> here are the definitions of the classes:
>>>>>>> 
>>>>>>> (defclass department ()
>>>>>>>   ((university :initarg :university :initform nil :accessor
>>>>>>> department-university
>>>>>>>                :index t)
>>>>>>>    (official-name :initarg :official-name :initform nil :accessor
>>>>>>> official-name)
>>>>>>>    (common-name :initarg :common-name :initform nil :accessor common-name)
>>>>>>>    (abbreviation :initarg :abbreviation :initform nil :accessor
>>>>>>> abbreviation
>>>>>>>                  :index t))
>>>>>>>   (:metaclass ele:persistent-metaclass)
>>>>>>>   (:documentation "A department has a bunch of course listings."))
>>>>>>> 
>>>>>>> (defclass material ()
>>>>>>>   ((title :initarg :title :initform nil :accessor material-title
>>>>>>>           :index t)
>>>>>>>    (authors :initarg :authors :initform nil :accessor material-authors) ;;
>>>>>>> a list of
>>>>>>> authors
>>>>>>>    (edition :initarg :edition :initform nil :accessor material-edition)
>>>>>>>    (isbn :initarg :isbn :initform nil :accessor material-isbn
>>>>>>>          :index t)
>>>>>>>    (asin :initarg :asin :initform nil :accessor material-asin
>>>>>>>          :index t
>>>>>>>          :documentation "An Amazon.com identifier that uniquely identifies
>>>>>>> the material")
>>>>>>>    (image-uri :initarg :image-uri :initform nil :accessor
>>>>>>> material-image-uri))
>>>>>>>   (:metaclass ele:persistent-metaclass))
>>>>>>> 
>>>>>>> Thanks,
>>>>>>> Red
>>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> elephant-devel site list
>>>>>> elephant-devel at common-lisp.net
>>>>>> http://common-lisp.net/mailman/listinfo/elephant-devel
>>>>>> 
>>>>>> _______________________________________________
>>>>>> elephant-devel site list
>>>>>> elephant-devel at common-lisp.net
>>>>>> http://common-lisp.net/mailman/listinfo/elephant-devel
>>>>> 
>>>>> _______________________________________________
>>>>> elephant-devel site list
>>>>> elephant-devel at common-lisp.net
>>>>> http://common-lisp.net/mailman/listinfo/elephant-devel
>>>> 
>>>> 
>>>> _______________________________________________
>>>> elephant-devel site list
>>>> elephant-devel at common-lisp.net
>>>> http://common-lisp.net/mailman/listinfo/elephant-devel
>>>> 
>>> 
>>> _______________________________________________
>>> elephant-devel site list
>>> elephant-devel at common-lisp.net
>>> http://common-lisp.net/mailman/listinfo/elephant-devel
>> 
>> 
> 
> _______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel




From franks-muc at web.de  Sun Jan 10 22:26:16 2010
From: franks-muc at web.de (Frank Schorr)
Date: Sun, 10 Jan 2010 23:26:16 +0100
Subject: [elephant-devel] initialize-instance :after
Message-ID: <10627891@web.de>

(still on 0.9)

I defined an after method for initialize instance of a persistent class.
The after method is called when a new persistent object is created, as desired.

It appears that the method is also called when the persistent object is read from the store, which is not what I want.

a) Is this possible ?
b) If yes, what mechanism can I use to do some work only when a *new* object is created ?

Thank you 
Frank Schorr






___________________________________________________________
Preisknaller: WEB.DE DSL Flatrate f?r nur 16,99 Euro/mtl.! 
http://produkte.web.de/go/02/




From eslick at media.mit.edu  Sun Jan 10 22:30:56 2010
From: eslick at media.mit.edu (Ian Eslick)
Date: Sun, 10 Jan 2010 17:30:56 -0500
Subject: [elephant-devel] initialize-instance :after
In-Reply-To: <10627891@web.de>
References: <10627891@web.de>
Message-ID: <73C0D3B2-50A0-4FD0-990D-F0B087B5068B@media.mit.edu>

We introduced recreate-instance in 1.0 which does not call your initialize-instance when existing instances are pulled from the DB.  You are not the first to have this problem.  ;)  Under the new system, you'll use initialize-instance which should have the expected behavior now of only acting at actual instance creation time.

Ian

On Jan 10, 2010, at 5:26 PM, Frank Schorr wrote:

> (still on 0.9)
> 
> I defined an after method for initialize instance of a persistent class.
> The after method is called when a new persistent object is created, as desired.
> 
> It appears that the method is also called when the persistent object is read from the store, which is not what I want.
> 
> a) Is this possible ?
> b) If yes, what mechanism can I use to do some work only when a *new* object is created ?
> 
> Thank you 
> Frank Schorr
> 
> 
> 
> 
> 
> 
> ___________________________________________________________
> Preisknaller: WEB.DE DSL Flatrate f?r nur 16,99 Euro/mtl.! 
> http://produkte.web.de/go/02/
> 
> 
> _______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel




From eslick at media.mit.edu  Sun Jan 10 23:14:27 2010
From: eslick at media.mit.edu (Ian Eslick)
Date: Sun, 10 Jan 2010 18:14:27 -0500
Subject: [elephant-devel] upgrade from 0.9 to 1.0
In-Reply-To: <3249935@web.de>
References: <3249935@web.de>
Message-ID: <D928A966-3A12-47E9-A52D-BC2D6EEFDB91@media.mit.edu>

I know we have pre-build Elephant DLLs for 4.5 which should work with 1.0.  Is that configuration working for everyone?

What's the current status of LW and BDB 4.7?  I only have access to LW 5.1 at the moment (Personal Edition for 6 is not out yet) so will not be able to help debug 6.0.  It will also take me a bit to find time to remember all the details of getting a windows machine to run elephant.  I should do it eventually in order to help test the 1.0 release, but it may be another week before I can get to this one.

Thank you,
Ian

On Jan 6, 2010, at 4:36 AM, Frank Schorr wrote:

> Hi Plamen,
> I had BDB running in one of the earlier versions of elephant. 
> You should be aware that BDB blocks under LW/win if multiple threads access the db.
> That is why I am using the postmodern backend. It is simple, stable and I don't have to care about performance.
> Still, I will try to get BDB up again and let you know.
> Best regards,
> Frank
> 
> 
>> -----Urspr?ngliche Nachricht-----
>> Von: "Plamen ." <plamen.usenet at gmail.com>
>> Gesendet: 05.01.10 16:56:55
>> An: Elephant bugs and development <elephant-devel at common-lisp.net>
>> Betreff: Re: [elephant-devel] upgrade from 0.9 to 1.0
> 
> 
>> Hello Frank, if you get Elephant & BDB running under LWW, I would be
>> interested in the result - see the LispWorks/Berkley post from last
>> month for details.
>> 
>> Regards
>> Plamen
>> 
> 
> ___________________________________________________________
> Preisknaller: WEB.DE DSL Flatrate f?r nur 16,99 Euro/mtl.! 
> http://produkte.web.de/go/02/
> 
> 
> _______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel




From plamen.usenet at gmail.com  Mon Jan 11 19:41:16 2010
From: plamen.usenet at gmail.com (Plamen .)
Date: Mon, 11 Jan 2010 20:41:16 +0100
Subject: [elephant-devel] upgrade from 0.9 to 1.0
In-Reply-To: <3249935@web.de>
References: <3249935@web.de>
Message-ID: <fd5f17a41001111141p37dc4197h7860f60443891883@mail.gmail.com>

Hello Frank,

Ian and Elliott Slaughter helped me already to at least can compile
some time ago under Windows/Cygwin the BDB 4.7, but we stuck in other
problems. I have LW 6, so - if I can help in any way to test - please
let me know - just my C/C++ knowledge is pretty dusty and I got stuck
in a couple of situations which I can't resolve so quickly as I would
wish.

>From what I did until yet - there is actually no problem with the
Elephant/Lisp source for running BDB under LWW 5 and 6, but only
compilation problems of the libberkeley-db.c - compiling it under
Cygwin (1.5) has the prolem, that ssize_t is declared differently in
BDB and Cygwin/GCC which even after successsful compilation brings
problems with pointer alignment if I understand the problem correctly.
I couldn't manage to solve the problem enought quick. Compiling
elephant under VC++ 2008 brings te problem (except the whole cration
of a valid Win32-DLL project aroound it and moving a lot of
declarations around to can work with VC++ 2008) that "errno" used as
parameter in some of the libberkley-db.c functions should be renamed
to something which doesn't clash with the "errno"-POSIX-macro -
otherwise one sees a disassembly of a statement like "*errno = 13"
translated to "call [_errno]" in assembler in producing "Illegal
memory exception"s... After correcting that (with the help of the LW
team) I got some "Bad pointer" errors from BDB after having created a
BDB-database, for which I didn't had enoght time - curently I use
cl-prevalence as a interim solution until BDB works again under
Windows.

So - again - if I can help (with preferrably the Lisp part and LWW6)
somehow after one manages to compile the libberkeley-db.c in a correct
way - please let me know - I would be happy to can use Elephant again.

Regards
Plamen

On Wed, Jan 6, 2010 at 10:36 AM, Frank Schorr <franks-muc at web.de> wrote:
> Hi Plamen,
> I had BDB running in one of the earlier versions of elephant.
> You should be aware that BDB blocks under LW/win if multiple threads access the db.
> That is why I am using the postmodern backend. It is simple, stable and I don't have to care about performance.
> Still, I will try to get BDB up again and let you know.
> Best regards,
> Frank
>
>
>> -----Urspr?ngliche Nachricht-----
>> Von: "Plamen ." <plamen.usenet at gmail.com>
>> Gesendet: 05.01.10 16:56:55
>> An: Elephant bugs and development <elephant-devel at common-lisp.net>
>> Betreff: Re: [elephant-devel] upgrade from 0.9 to 1.0
>
>
>> Hello Frank, if you get Elephant & BDB running under LWW, I would be
>> interested in the result - see the LispWorks/Berkley post from last
>> month for details.
>>
>> Regards
>> Plamen
>>
>
> ___________________________________________________________
> Preisknaller: WEB.DE DSL Flatrate f?r nur 16,99 Euro/mtl.!
> http://produkte.web.de/go/02/
>
>
> _______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel
>



From franks-muc at web.de  Wed Jan 13 23:00:36 2010
From: franks-muc at web.de (Frank Schorr)
Date: Thu, 14 Jan 2010 00:00:36 +0100
Subject: [elephant-devel] upgrade from 0.9 to 1.0
Message-ID: <16292451@web.de>

Hi Ian:

Now I managed to build the libberkeley-db.dll with BDB 4.5 with these commands:


 gcc -L'/cygdrive/C/Programme/Oracle/Berkeley DB 4.5.20/lib/' \
    -I'/cygdrive/C/Programme/Oracle/Berkeley DB 4.5.20/include/' \
    -llibdb45 \
    -mno-cygwin \
    -mwindows \
    -Wall \
    -c \
    -std=c99 \
    "/cygdrive/c/lisp/libraries/elephant-1.0/src/db-bdb/libberkeley-db.c"

dlltool -z "/cygdrive/C/lisp/libraries/elephant-1.0/src/db-bdb/libberkeley-db.def" \
    --export-all-symbols \
    -e exports.o \
    -l '/cygdrive/C/lisp/libraries/elephant-1.0/src/db-bdb/libberkeley-db.lib' \
    '/cygdrive/C/lisp/libraries/elephant-1.0/src/db-bdb/libberkeley-db.o'
 
gcc -L'/cygdrive/C/Programme/Oracle/Berkeley DB 4.5.20/bin/' \
    -I'/cygdrive/C/Programme/Oracle/Berkeley DB 4.5.20/include/' \
    -llibdb45 \
    -shared \
    -mno-cygwin \
    -mwindows \
    -Wall \
    '/cygdrive/C/lisp/libraries/elephant-1.0/src/db-bdb/libberkeley-db.o' \
    exports.o \
    -o '/cygdrive/C/lisp/libraries/elephant-1.0/src/db-bdb/libberkeley-db.dll'

 
I will amend the asdf file to do this automatically within the next couple of days. 
The library file (here: "libdb45") is defined in the asdf. Shouldn't this happen in my-config.sexp ?

I can load :ele-bdb
This is the output with some warnigs you might be interested in:

; loading system definition from c:\lisp\libraries\elephant-1.0\elephant.asd into
; #<The ASDF0 package, 0/16 internal, 0/16 external>
; Loading text file c:\lisp\libraries\elephant-1.0\elephant.asd
; registering #<SYSTEM ELEPHANT 200E75BF> as ELEPHANT
;; Creating system COMMON-LISP-USER::ELEPHANT->SRC->UTILS
;; Creating system COMMON-LISP-USER::ELEPHANT->SRC->MEMUTIL
;; Creating system COMMON-LISP-USER::ELEPHANT->SRC->ELEPHANT
;; Creating system COMMON-LISP-USER::ELEPHANT->SRC
;; Creating system COMMON-LISP-USER::ELEPHANT
; loading system definition from c:\lisp\libraries\cl-base64-3.3.2\cl-base64.asd into
; #<The ASDF0 package, 0/16 internal, 0/16 external>
; Loading text file c:\lisp\libraries\cl-base64-3.3.2\cl-base64.asd
; registering #<SYSTEM CL-BASE64 21ADC563> as CL-BASE64
;; Creating system COMMON-LISP-USER::CL-BASE64
; registering #<SYSTEM CL-BASE64-TESTS 200F500B> as CL-BASE64-TESTS
;; Creating system COMMON-LISP-USER::CL-BASE64-TESTS
; loading system definition from c:\lisp\libraries\uffi-1.5.18\uffi.asd into #<The ASDF0 package, 0/16 internal, 0/16 external>
; Loading text file c:\lisp\libraries\uffi-1.5.18\uffi.asd
; registering #<SYSTEM UFFI 21AD98E7> as UFFI
;; Creating system COMMON-LISP-USER::UFFI->SRC
;; Creating system COMMON-LISP-USER::UFFI
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\uffi-1.5.18\src\package.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\uffi-1.5.18\src\primitives.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\uffi-1.5.18\src\objects.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\uffi-1.5.18\src\aggregates.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\uffi-1.5.18\src\functions.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\uffi-1.5.18\src\strings.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\uffi-1.5.18\src\libraries.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\uffi-1.5.18\src\os.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\cl-base64-3.3.2\package.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\cl-base64-3.3.2\encode.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\cl-base64-3.3.2\decode.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\utils\package.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\utils\convenience.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\utils\locks.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\utils\os.ofasl
Attempting to load libmemutil.dll...
Loaded c:\lisp\libraries\elephant-1.0\src\memutil\libmemutil.dll
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\memutil\memutil.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\package.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\variables.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\transactions.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\schemas.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\metaclasses.ofasl
Warning: (METHOD (SETF SLOT-DEFINITION-ALLOCATION) (T PERSISTENT-SLOT-DEFINITION)) defined more than once in c:\lisp\libraries\elephant-1.0\src\elephant\metaclasses.lisp.
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\classes.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\cache.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\serializer.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\controller.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\schema-evolution.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\cached-slots.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\collections.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\indexed-slots.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\pset.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\set-valued-slots.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\associations.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\serializer1.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\serializer2.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\unicode.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\migrate.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\gc.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\query.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\data-store-api.ofasl


Warnings:
(METHOD (SETF SLOT-DEFINITION-ALLOCATION) (T ELEPHANT::PERSISTENT-SLOT-DEFINITION)) defined more than once in c:\lisp\libraries\elephant-1.0\src\elephant\metaclasses.lisp.
NIL 

---- Done ----
; loading system definition from c:\lisp\libraries\elephant-1.0\ele-bdb.asd into
; #<The ASDF0 package, 0/16 internal, 0/16 external>
; Loading text file c:\lisp\libraries\elephant-1.0\ele-bdb.asd
Warning: (DEFCLASS ELEPHANT-C-SOURCE) being redefined in c:\lisp\libraries\elephant-1.0\ele-bdb.asd (previously in c:\lisp\libraries\elephant-1.0\elephant.asd).
; registering #<SYSTEM ELE-BDB 21C5E92B> as ELE-BDB
;; Creating system COMMON-LISP-USER::ELE-BDB->SRC->DB-BDB
;; Creating system COMMON-LISP-USER::ELE-BDB->SRC
;; Creating system COMMON-LISP-USER::ELE-BDB
Attempting to load libmemutil.dll...
Loaded c:\lisp\libraries\elephant-1.0\src\memutil\libmemutil.dll
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\memutil\memutil.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\db-bdb\package.ofasl
Loading C:/Programme/Oracle/Berkeley DB 4.7.25/bin/libdb47.dll
Attempting to load libberkeley-db.dll...
Loaded c:\lisp\libraries\elephant-1.0\src\db-bdb\libberkeley-db.dll
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\db-bdb\berkeley-constants.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\db-bdb\berkeley-db.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\db-bdb\bdb-controller.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\db-bdb\bdb-slots.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\db-bdb\bdb-collections.ofasl
; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\db-bdb\bdb-transactions.ofasl

Warnings:
(DEFCLASS ELEPHANT-SYSTEM:ELEPHANT-C-SOURCE) being redefined in c:\lisp\libraries\elephant-1.0\ele-bdb.asd (previously in c:\lisp\libraries\elephant-1.0\elephant.asd).
NIL 


(setf *db-spec* '(:BDB #p"c:/temp/testdb/"))
(ele:open-store *db-spec*)

throws this error:

Error: Berkeley DB error #22: Invalid argument

Call to (METHOD ELEPHANT::OPEN-CONTROLLER (DB-BDB::BDB-STORE-CONTROLLER)) (offset 295)

Call to CLOS::METHOD-COMBINATION-TEMPLATE (offset 62)

Call to OPEN-STORE (offset 66)

Call to EVAL (offset 113)
  EXP : (OPEN-STORE *DB-SPEC*)

Call to EDITOR::EDITOR-EVAL (offset 177)
  EDITOR:BUFFER  : :DONT-KNOW
  EDITOR::SEXP   : (OPEN-STORE *DB-SPEC*)
  EDITOR::ERRORP : T

Call to (SUBFUNCTION 3 (SUBFUNCTION 1 EDITOR::REGION-LISP-EVAL)) (offset 26)
  EDITOR::FORM  : (OPEN-STORE *DB-SPEC*)
  EDITOR:BUFFER : #<EDITOR:BUFFER work.lisp>


sparse information...
Do you have a global place for setting the debug information ?

Best regards,
Frank


> -----Urspr?ngliche Nachricht-----
> Von: "Ian Eslick" <eslick at media.mit.edu>
> Gesendet: 11.01.10 00:16:56
> An: Elephant bugs and development <elephant-devel at common-lisp.net>
> Betreff: Re: [elephant-devel] upgrade from 0.9 to 1.0
> Priorit?t: Niedrig


> I know we have pre-build Elephant DLLs for 4.5 which should work with 1.0.  Is that configuration working for everyone?
> 
> What's the current status of LW and BDB 4.7?  I only have access to LW 5.1 at the moment (Personal Edition for 6 is not out yet) so will not be able to help debug 6.0.  It will also take me a bit to find time to remember all the details of getting a windows machine to run elephant.  I should do it eventually in order to help test the 1.0 release, but it may be another week before I can get to this one.
> 
> Thank you,
> Ian

______________________________________________________
GRATIS f?r alle WEB.DE-Nutzer: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://movieflat.web.de




From eslick at media.mit.edu  Wed Jan 13 23:10:43 2010
From: eslick at media.mit.edu (Ian Eslick)
Date: Wed, 13 Jan 2010 15:10:43 -0800
Subject: [elephant-devel] upgrade from 0.9 to 1.0
In-Reply-To: <16292451@web.de>
References: <16292451@web.de>
Message-ID: <F0286C48-64C4-4103-8282-A04AF94058BF@media.mit.edu>

Are you unable to build 4.7?

(I presume you've got my-config.sexp pointing at 4.5 and telling the code to use the 4.5 constants)

Error #22 basically means that some constant passed to the C function open-store are incorrect.  While in the lisp debugger, if you attach to the lisp using GDB you can often see the C stack to see which function failed.  Generally, debugging these errors is really annoying - I haven't found a clean way of getting the real debug information out of these calls.

One quick suggestion.  Try doing an open-store with the :deadlock-detect nil keyword argument.  I can't remember for sure whether that is dependent on 4.6 or 4.7 but it's worth trying.

Best,
Ian

On Jan 13, 2010, at 3:00 PM, Frank Schorr wrote:

> Hi Ian:
> 
> Now I managed to build the libberkeley-db.dll with BDB 4.5 with these commands:
> 
> 
> gcc -L'/cygdrive/C/Programme/Oracle/Berkeley DB 4.5.20/lib/' \
>    -I'/cygdrive/C/Programme/Oracle/Berkeley DB 4.5.20/include/' \
>    -llibdb45 \
>    -mno-cygwin \
>    -mwindows \
>    -Wall \
>    -c \
>    -std=c99 \
>    "/cygdrive/c/lisp/libraries/elephant-1.0/src/db-bdb/libberkeley-db.c"
> 
> dlltool -z "/cygdrive/C/lisp/libraries/elephant-1.0/src/db-bdb/libberkeley-db.def" \
>    --export-all-symbols \
>    -e exports.o \
>    -l '/cygdrive/C/lisp/libraries/elephant-1.0/src/db-bdb/libberkeley-db.lib' \
>    '/cygdrive/C/lisp/libraries/elephant-1.0/src/db-bdb/libberkeley-db.o'
> 
> gcc -L'/cygdrive/C/Programme/Oracle/Berkeley DB 4.5.20/bin/' \
>    -I'/cygdrive/C/Programme/Oracle/Berkeley DB 4.5.20/include/' \
>    -llibdb45 \
>    -shared \
>    -mno-cygwin \
>    -mwindows \
>    -Wall \
>    '/cygdrive/C/lisp/libraries/elephant-1.0/src/db-bdb/libberkeley-db.o' \
>    exports.o \
>    -o '/cygdrive/C/lisp/libraries/elephant-1.0/src/db-bdb/libberkeley-db.dll'
> 
> 
> I will amend the asdf file to do this automatically within the next couple of days. 
> The library file (here: "libdb45") is defined in the asdf. Shouldn't this happen in my-config.sexp ?
> 
> I can load :ele-bdb
> This is the output with some warnigs you might be interested in:
> 
> ; loading system definition from c:\lisp\libraries\elephant-1.0\elephant.asd into
> ; #<The ASDF0 package, 0/16 internal, 0/16 external>
> ; Loading text file c:\lisp\libraries\elephant-1.0\elephant.asd
> ; registering #<SYSTEM ELEPHANT 200E75BF> as ELEPHANT
> ;; Creating system COMMON-LISP-USER::ELEPHANT->SRC->UTILS
> ;; Creating system COMMON-LISP-USER::ELEPHANT->SRC->MEMUTIL
> ;; Creating system COMMON-LISP-USER::ELEPHANT->SRC->ELEPHANT
> ;; Creating system COMMON-LISP-USER::ELEPHANT->SRC
> ;; Creating system COMMON-LISP-USER::ELEPHANT
> ; loading system definition from c:\lisp\libraries\cl-base64-3.3.2\cl-base64.asd into
> ; #<The ASDF0 package, 0/16 internal, 0/16 external>
> ; Loading text file c:\lisp\libraries\cl-base64-3.3.2\cl-base64.asd
> ; registering #<SYSTEM CL-BASE64 21ADC563> as CL-BASE64
> ;; Creating system COMMON-LISP-USER::CL-BASE64
> ; registering #<SYSTEM CL-BASE64-TESTS 200F500B> as CL-BASE64-TESTS
> ;; Creating system COMMON-LISP-USER::CL-BASE64-TESTS
> ; loading system definition from c:\lisp\libraries\uffi-1.5.18\uffi.asd into #<The ASDF0 package, 0/16 internal, 0/16 external>
> ; Loading text file c:\lisp\libraries\uffi-1.5.18\uffi.asd
> ; registering #<SYSTEM UFFI 21AD98E7> as UFFI
> ;; Creating system COMMON-LISP-USER::UFFI->SRC
> ;; Creating system COMMON-LISP-USER::UFFI
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\uffi-1.5.18\src\package.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\uffi-1.5.18\src\primitives.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\uffi-1.5.18\src\objects.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\uffi-1.5.18\src\aggregates.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\uffi-1.5.18\src\functions.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\uffi-1.5.18\src\strings.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\uffi-1.5.18\src\libraries.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\uffi-1.5.18\src\os.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\cl-base64-3.3.2\package.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\cl-base64-3.3.2\encode.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\cl-base64-3.3.2\decode.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\utils\package.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\utils\convenience.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\utils\locks.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\utils\os.ofasl
> Attempting to load libmemutil.dll...
> Loaded c:\lisp\libraries\elephant-1.0\src\memutil\libmemutil.dll
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\memutil\memutil.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\package.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\variables.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\transactions.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\schemas.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\metaclasses.ofasl
> Warning: (METHOD (SETF SLOT-DEFINITION-ALLOCATION) (T PERSISTENT-SLOT-DEFINITION)) defined more than once in c:\lisp\libraries\elephant-1.0\src\elephant\metaclasses.lisp.
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\classes.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\cache.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\serializer.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\controller.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\schema-evolution.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\cached-slots.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\collections.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\indexed-slots.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\pset.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\set-valued-slots.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\associations.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\serializer1.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\serializer2.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\unicode.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\migrate.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\gc.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\query.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\elephant\data-store-api.ofasl
> 
> 
> Warnings:
> (METHOD (SETF SLOT-DEFINITION-ALLOCATION) (T ELEPHANT::PERSISTENT-SLOT-DEFINITION)) defined more than once in c:\lisp\libraries\elephant-1.0\src\elephant\metaclasses.lisp.
> NIL 
> 
> ---- Done ----
> ; loading system definition from c:\lisp\libraries\elephant-1.0\ele-bdb.asd into
> ; #<The ASDF0 package, 0/16 internal, 0/16 external>
> ; Loading text file c:\lisp\libraries\elephant-1.0\ele-bdb.asd
> Warning: (DEFCLASS ELEPHANT-C-SOURCE) being redefined in c:\lisp\libraries\elephant-1.0\ele-bdb.asd (previously in c:\lisp\libraries\elephant-1.0\elephant.asd).
> ; registering #<SYSTEM ELE-BDB 21C5E92B> as ELE-BDB
> ;; Creating system COMMON-LISP-USER::ELE-BDB->SRC->DB-BDB
> ;; Creating system COMMON-LISP-USER::ELE-BDB->SRC
> ;; Creating system COMMON-LISP-USER::ELE-BDB
> Attempting to load libmemutil.dll...
> Loaded c:\lisp\libraries\elephant-1.0\src\memutil\libmemutil.dll
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\memutil\memutil.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\db-bdb\package.ofasl
> Loading C:/Programme/Oracle/Berkeley DB 4.7.25/bin/libdb47.dll
> Attempting to load libberkeley-db.dll...
> Loaded c:\lisp\libraries\elephant-1.0\src\db-bdb\libberkeley-db.dll
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\db-bdb\berkeley-constants.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\db-bdb\berkeley-db.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\db-bdb\bdb-controller.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\db-bdb\bdb-slots.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\db-bdb\bdb-collections.ofasl
> ; Loading fasl file c:\lisp\binaries\lispworks-5.0.2-win-i386\lisp\libraries\elephant-1.0\src\db-bdb\bdb-transactions.ofasl
> 
> Warnings:
> (DEFCLASS ELEPHANT-SYSTEM:ELEPHANT-C-SOURCE) being redefined in c:\lisp\libraries\elephant-1.0\ele-bdb.asd (previously in c:\lisp\libraries\elephant-1.0\elephant.asd).
> NIL 
> 
> 
> (setf *db-spec* '(:BDB #p"c:/temp/testdb/"))
> (ele:open-store *db-spec*)
> 
> throws this error:
> 
> Error: Berkeley DB error #22: Invalid argument
> 
> Call to (METHOD ELEPHANT::OPEN-CONTROLLER (DB-BDB::BDB-STORE-CONTROLLER)) (offset 295)
> 
> Call to CLOS::METHOD-COMBINATION-TEMPLATE (offset 62)
> 
> Call to OPEN-STORE (offset 66)
> 
> Call to EVAL (offset 113)
>  EXP : (OPEN-STORE *DB-SPEC*)
> 
> Call to EDITOR::EDITOR-EVAL (offset 177)
>  EDITOR:BUFFER  : :DONT-KNOW
>  EDITOR::SEXP   : (OPEN-STORE *DB-SPEC*)
>  EDITOR::ERRORP : T
> 
> Call to (SUBFUNCTION 3 (SUBFUNCTION 1 EDITOR::REGION-LISP-EVAL)) (offset 26)
>  EDITOR::FORM  : (OPEN-STORE *DB-SPEC*)
>  EDITOR:BUFFER : #<EDITOR:BUFFER work.lisp>
> 
> 
> sparse information...
> Do you have a global place for setting the debug information ?
> 
> Best regards,
> Frank
> 
> 
>> -----Urspr?ngliche Nachricht-----
>> Von: "Ian Eslick" <eslick at media.mit.edu>
>> Gesendet: 11.01.10 00:16:56
>> An: Elephant bugs and development <elephant-devel at common-lisp.net>
>> Betreff: Re: [elephant-devel] upgrade from 0.9 to 1.0
>> Priorit?t: Niedrig
> 
> 
>> I know we have pre-build Elephant DLLs for 4.5 which should work with 1.0.  Is that configuration working for everyone?
>> 
>> What's the current status of LW and BDB 4.7?  I only have access to LW 5.1 at the moment (Personal Edition for 6 is not out yet) so will not be able to help debug 6.0.  It will also take me a bit to find time to remember all the details of getting a windows machine to run elephant.  I should do it eventually in order to help test the 1.0 release, but it may be another week before I can get to this one.
>> 
>> Thank you,
>> Ian
> 
> ______________________________________________________
> GRATIS f?r alle WEB.DE-Nutzer: Die maxdome Movie-FLAT!
> Jetzt freischalten unter http://movieflat.web.de
> 
> 
> _______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel




From sky at viridian-project.de  Thu Jan 14 08:31:58 2010
From: sky at viridian-project.de (Leslie P. Polzer)
Date: Thu, 14 Jan 2010 09:31:58 +0100 (CET)
Subject: [elephant-devel] upgrade from 0.9 to 1.0
In-Reply-To: <F0286C48-64C4-4103-8282-A04AF94058BF@media.mit.edu>
References: <16292451@web.de>
	<F0286C48-64C4-4103-8282-A04AF94058BF@media.mit.edu>
Message-ID: <dd3cd7f2ffc2507b8147d5c615d2da33.squirrel@mail.stardawn.org>


Ian Eslick wrote:

> One quick suggestion.  Try doing an open-store with the :deadlock-detect nil keyword
> argument.  I can't remember for sure whether that is dependent on 4.6 or 4.7 but it's
> worth trying.

Default deadlock detection works with 4.5, 4.6 and 4.7.

  Leslie




From killerstorm at newmail.ru  Thu Jan 21 02:35:30 2010
From: killerstorm at newmail.ru (Alex Mizrahi)
Date: Thu, 21 Jan 2010 04:35:30 +0200
Subject: [elephant-devel] initialize-instance :after
References: <10627891@web.de>
	<73C0D3B2-50A0-4FD0-990D-F0B087B5068B@media.mit.edu>
Message-ID: <hj8ehq$ttj$1@ger.gmane.org>

 IE> We introduced recreate-instance in 1.0 which does not call your
 IE> initialize-instance when existing instances are pulled from the DB.
 IE> You are not the first to have this problem.  ;)  Under the new system,
 IE> you'll use initialize-instance which should have the expected behavior
 IE> now of only acting at actual instance creation time.

We had that in 0.9.x branch too. 






From eslick at media.mit.edu  Thu Jan 21 02:46:19 2010
From: eslick at media.mit.edu (Ian Eslick)
Date: Wed, 20 Jan 2010 18:46:19 -0800
Subject: [elephant-devel] initialize-instance :after
In-Reply-To: <hj8ehq$ttj$1@ger.gmane.org>
References: <10627891@web.de>
	<73C0D3B2-50A0-4FD0-990D-F0B087B5068B@media.mit.edu>
	<hj8ehq$ttj$1@ger.gmane.org>
Message-ID: <39DB3810-046D-4FC8-84C6-962259166B7E@media.mit.edu>

But not, I believe, in the actual 0.9 release.  0.9.1 may have had it.  

On Jan 20, 2010, at 6:35 PM, Alex Mizrahi wrote:

> IE> We introduced recreate-instance in 1.0 which does not call your
> IE> initialize-instance when existing instances are pulled from the DB.
> IE> You are not the first to have this problem.  ;)  Under the new system,
> IE> you'll use initialize-instance which should have the expected behavior
> IE> now of only acting at actual instance creation time.
> 
> We had that in 0.9.x branch too. 
> 
> 
> 
> 
> _______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel




From spacebat at ubermonkey.net  Mon Jan 25 22:18:23 2010
From: spacebat at ubermonkey.net (Andrew Kirkpatrick)
Date: Tue, 26 Jan 2010 08:48:23 +1030
Subject: [elephant-devel] Possible bug in sql-controller.lisp
Message-ID: <4B5E18AF.30408@ubermonkey.net>

Hi,

I'm trying to get elephant working with sqlite on sbcl, and I'm using 
clbuild to retrieve and set up systems. However, evaluating the 
following form led to an error:

(defvar *elephant-store*
   (open-store '(:clsql (:sqlite3 "/tmp/test.db"))))

The error was:

Execution of a form compiled with errors.
Form:
   (HANDLER-CASE (QUERY select count(*) from keyvalue)
               ((SQL-DATABASE-ERROR NIL NIL)))
Compile-time error:
   (in macroexpansion of (HANDLER-CASE (CLSQL-SYS:QUERY "select count(*) 
from keyvalue") ((CLSQL-SYS:SQL-DATABASE-ERROR NIL NIL))))
(hint: For more precise location, try *BREAK-ON-SIGNALS*.)
error while parsing arguments to DESTRUCTURING-BIND:
   invalid number of elements in
     ((CLSQL-SYS:SQL-DATABASE-ERROR NIL NIL))
   to satisfy lambda list
     (TYPE SB-IMPL::LL &BODY SB-IMPL::BODY):
   at least 2 expected, but 1 found
[Condition of type SB-INT:COMPILED-PROGRAM-ERROR]

Looking at the source, it appears there was an extra set of parentheses 
around SQL-DATABASE-ERROR () NIL on sql-controller.lisp line 301. I 
removed one set of parens, deleted the corresponding fasl and 
subsequently the form evaluated without error.

Then trying to use the store I ran into another problem that smells of 
FFI, but that's for another post.

Cheers,
--
Andrew Kirkpatrick

"The first rule of Perl Club... has subscript 0.
  Unless you changed $[.
  But don't!"

-- blazar on perlmonks.org



From henrik at evahjelte.com  Mon Jan 25 23:16:51 2010
From: henrik at evahjelte.com (Henrik Hjelte)
Date: Tue, 26 Jan 2010 00:16:51 +0100
Subject: [elephant-devel] Possible bug in sql-controller.lisp
In-Reply-To: <4B5E18AF.30408@ubermonkey.net>
References: <4B5E18AF.30408@ubermonkey.net>
Message-ID: <50e8e4f61001251516ia1e9c90i6127af639264591f@mail.gmail.com>

On Mon, Jan 25, 2010 at 11:18 PM, Andrew Kirkpatrick
<spacebat at ubermonkey.net> wrote:
> Hi,
>
> I'm trying to get elephant working with sqlite on sbcl, and I'm using
> clbuild to retrieve and set up systems.

I am not sure the sql backend of elephant is up to date. It is largely
unmaintained, and will probably be dropped soon. I strongly suggest
either the BDB or Postmodern backend.

BDB is fast on a single computer, Postmodern is scalable across
threads, processes and computers.
The sql backend is actually neither.

Also, if you have downloaded from clbuild make sure that elephants
loads the real uffi.asd not the uffi.asd file in the cffi folder (see
older posts on the mailing list).

> Then trying to use the store I ran into another problem that smells of
> FFI, but that's for another post.

My guess is that it is the uffi problem.

I take this opportunity to submit a patch I tried to send earlier, it
detects this problem, intended for elephant-1.0

Hope this helps, even though it was not a direct answer to your question,

Henrik Hjelte
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cffi-uffi.patch
Type: application/octet-stream
Size: 14255 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/elephant-devel/attachments/20100126/7bab477b/attachment.obj>