| Flor,
I'm not sure if this is a good idea or not, I've never tried this myself, but have you looked into registering with EOObserverCenter for EOObserving.objectWillChange(Object)?
Sounds a bit scary to me as far as possibly introducing performance, and other various, issues, but just might do the trick for you. On Oct 10, 2006, at 12:03 PM, Florijan Stamenkovic wrote: Hi all,
I am trying to find a way to detect changes eos just *after* they happen. If possible the implementation should consider the Author object changed, if one of his Books has been unassociated / deleted.
I tried with EOEditingContext notifications, but they are posted only at save time. I also could not find anything to fit the purpose in Project Wonder, yet.
If nothing like that exists, I am thinking of implementing it through a notification posting EOGenericRecord subclass. Any comments or tips about this?
One more question: EOs are not automatically removed from to-many relationships after being deleted, even when their delete rule is set to nullify. Is this another client side EOClassDescription bug, or a standard behavior?
Thanks Flor _______________________________________________ Do not post admin requests to the list. They will be ignored. Help/Unsubscribe/Update your Subscription:
|
_______________________________________________
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]
