SR> I'm sorry to hear that my patch caused so many issues with postmodern SR> and I'm quite keen to investigate the cause of this. I'll be SR> installing setting up the postmodern backend and seeing if I can track SR> down the causes of these problems.
looks like it's related to some deep weirdness of db-postmodern implementation, and i think i've almost tracked this down, so i don't recommend anyone spending time on this. (well, until/if i'll give up..) however i'd like to see comments about class "persistent" -- it doesn't even recieve shared-initialize, are there any reasons for special threating of it? and are there reasons for using this recreate initialization sequence for class "persistent"? only instances of classes of persistent-metaclass metaclass (e.g. persistent-object) can have persistent slots, so it makes sense to bypass make-instance only for such classes. other classes have quite SR> As to where to go from here I do agree with robert on this and that it SR> is nice to have the seperation between the creation and restoration of SR> instances although I think this needs to be done with a well thought SR> out protocol. SR> cheers, SR> sean. ) (With-best-regards '(Alex Mizrahi) :aka 'killer_storm) "Hanging In The Balance Of Deceit And Blasphemy") _______________________________________________ elephant-devel site list elephant-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/elephant-devel
