On Feb 23, 2008, at 4:03 AM, Leslie P. Polzer wrote:
2) The persistent-metaclass would be extended to support multiple
class indexes; one for each store controller instances exist in.
I suppose that's the architectural issue you were talking about,
but which I didn't fully grasp because I haven't looked at the code.
There are some secondary architectural issues that are more
complicated and involve how the system keeps track of mismatches
between a data store and a class definition, how class re-definition
is handled to add/drop indices, etc.
I'll do # 1-4 now since it doesn't really effect anyone but you and
maintains the current behavior for anyone else. I can't sign up for
#5-6.
I'd do #5 and #6, in principle, but this issue is not really big
enough an itch for me to scratch it right now.
Great! I've implemented #1-3 already and #4 is easy. I am just
testing them now. If you turn off multi-store support everything
passes, just a few snafus in the multi-store case.
Perhaps it would be best to archive this discussion (or the results
of it) in a ticket and then do it later.
I'll take care of that when I check in the new code.
Leslie
--
My personal blog: http://blog.viridian-project.de/
_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
