On Wed, May 4, 2011 at 7:00 PM, Ramon Leon <[email protected]> wrote:
> My general approach would be this sequence of steps, let's assume his > class is called Person in collection var name people. > > If Person has an initialize method, rename it to initializeOld. > Change superclass of Person to SDActiveRecord. > Person warmUp. to setup the store for this new class. > people do: [:e | e initialize ] to invoke active records initialize > setting up it's necessary inst vars and marking all people as new > rename Person>>initializeOld back to Person>>initialize. > people do: [:e | e save ] > > Migration complete. > > Thanks a lot Ramon, I add this to Pharocasts. Laurent > -- > Ramon Leon > http://onsmalltalk.com > > > On Wed, May 4, 2011 at 4:58 AM, laurent laffont > <[email protected]> wrote: > > > > Someone knows ? > > Laurent > > > > > > ---------- Forwarded message ---------- > > From: Bernat Romagosa <[email protected]> > > Date: Wed, May 4, 2011 at 1:37 PM > > Subject: [Pharocasts] New comment on SandstoneDb, simple ActiveRecord > style > > persistence.... > > To: [email protected] > > > > > > Bernat Romagosa has left a new comment on your post "SandstoneDb, simple > > ActiveRecord style persistence...": > > > > I was trying to migrate a simple image-based persistence app into > Sandstone, > > so I just recompiled my biz objects to be subclasses of SDActiveRecord, > but > > of course the objects I want to save are already created and "floating" > in > > the image, so when I try to save them I get an error as many instvars > > haven't been initialized upon creating these objects (as they were > already > > there). > > > > Is there a way to automatically do this? > > > > Thanks! > > > > Bernat. > > > > > > > > Posted by Bernat Romagosa to Pharocasts at May 4, 2011 4:37 AM > > >
