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@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
