Re: Partially saving the object graph. How? (Jean Pierre Malrieu)
Re: Partially saving the object graph. How? (Jean Pierre Malrieu)
- Subject: Re: Partially saving the object graph. How? (Jean Pierre Malrieu)
- From: Jean Pierre Malrieu <email@hidden>
- Date: Tue, 20 Mar 2007 09:53:05 +0100
Gary Teter wrote:
I'm going to agree with Chuck and the rest that this is probably a
bad idea.
You, Chuck, "and the rest" have convinced me. I am not going to fight
EOF.
However, if I had my heart set on doing it, I'd look at creating an
EOAdaptorChannel delegate and implement the
adaptorChannelWillPerformOperations method so it removes the adaptor
operations pertaining to entity B.
But I don't think EOF will be very happy that you're doing this. That
means you'll have enterprise objects and snapshots in memory that
don't correspond to rows in the database, so you may need to also
implement an EODatabaseContext delegate for
databaseContextFailedToFetchObject and/or the various
databaseContextShouldFetch methods.
You are scaring me more than Chuck's EOF bus.
Perhaps a better solution would be to remap entity B to a different
table for this special application so it's not cluttering up the real
entity B table?
This is clearly the easier solution for me. I won't rewrite any code.
I'll go that way. This will imply more SQL operations than really
needed, but only twice as much, so I don't think this will be a big
deal.
Thanks a lot.
JPM
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden