Yep, store gets opened on application start, before session-init is called.
Also, moving init-dummy to open-store :after pushes the problem further,
then I get a BDB-DB-ERROR when calling
(elephant::get-db-schemas (weblocks-elephant::elephant-controller
*my-elephant-store*) 'product-item)
- th
BDB 4.5 for back-end.
I'm using elephant-unstable, pulled last week.
I'm elephant this via Weblocks, so I'm assuming the store is open by the
time the init-session for Weblocks app is called. Maybe I should check on
that - it's possible that the store is not in fully open state?
Yarek
On Thu, D
Which version of elephant are you using?
Which backend are you using? If BDB, which version?
I presume *store-controller* open and reachable from the package you
are in?
Looks like the elephant store isn't in the proper state (e.g. was
closed and *store-controller* was not zeroed out).
On D
I've converted my weblocks app to use elephant. One of the first things I
do is to initialize some variables. One of the variables is a "demo" item,
that I use as a placeholder until the user choses something more specific.
I'm having trouble initializing the dummy. Here is my code:
(defun init
