[Cl-perec-devel] Another multi-db bug?
Leslie P. Polzer
leslie.polzer at gmx.net
Wed Aug 27 08:15:23 UTC 2008
> the problem is that both databases are in the same
> "computed-universe", so when a class is exported in one database then
> it gets "computed" (iow, valid) so the export is considered done when
> accessing the next database.
I suppose that slot should be a list that stores which databases
have been updated and which have not.
> what's your use-case for using two databases? is it schema evolution
> and the involved data migration?
Performance, separation of concerns and convenience e.g. when backing-up
I need to have several semantically and referentially self-contained
collections of data (e.g. users and their messages).
Each Lisp process has access to exactly one of this and doesn't need
access to the others.
In addition, there is one that is shared by all others, and I need
to clone objects off it. It's some kind of instantiation.
Talking Plato, exactly one of my databases is a shared collection of
"ideals" and the others are separate real-world instances of these
Thus each process needs access to the public shared storage and to its
own private storage.
I'd appreciate alternate proposals, but so far this has shown to be
the most efficient way.
More information about the cl-perec-devel