| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
Gary Teter wrote:
I'm going to agree with Chuck and the rest that this is probably a bad idea.
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?
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: http://lists.apple.com/mailman/options/webobjects-dev/email@hidden
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.