Ok, fair enough. So would you recommend using a different persistence framework on the client, or just avoid doing offline storage at all?
John On Wed, Apr 15, 2009 at 2:55 PM, Mike Schrag <[email protected]> wrote: > On Wed, Apr 15, 2009 at 12:27 PM, Chuck Hill <[email protected]> >>> wrote: >>> Hmmm, a separate EOModelGroup, and EOF stack might be a good start. But >>> I think you are going to need to create the objects in the local database >>> and then copy the data over. >>> >>> How would I get started with that? >>> >>> Can I use the same model? Same EO classes? Conjecture is ok. >>> >> I am not sure and don't have the time to sit down and play with it. You >> would need to create a new EOModelGroup, load your models into it, change >> their connection dictionaries and then use that model group to create new >> EOEditingContexts with. Beware of any EOF method named default* if you do >> this. PracticalWebObjects has code for copying graphs of EOs. I don't know >> if it would work in this situation or not. You should be able to use the >> same classes. >> > for the record, this smells of "terrible idea" ... > > ms > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/webobjects-dev/johnthuss%40gmail.com > > This email sent to [email protected] >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
