As a first idea, you could make an EC subclass that was able to identify these ready only instances and not call super in deleteObject().
Chuck On 2016-03-21, 1:17 PM, "webobjects-dev-bounces+chill=gevityinc....@lists.apple.com on behalf of OC" <webobjects-dev-bounces+chill=gevityinc....@lists.apple.com on behalf of o...@ocs.cz> wrote: >Hello there, > >is there a trick to “undelete” an object in editing context? > >Before saveChanges, I go through ec.deletedObjects(), and in some very special >cases, I might find that an object should NOT be deleted. Just like it has >never been added to deletedObjects at all. > >I've tried to insertObject it immediately; that works all right for the object >itself, but still removes its owned :1 relationships, which is also quite >wrong. > >Is there a way to do it right? > >Note: if there was a way to mark specific objects as read-only (never to be >deleted, never to be updated), it would be even better; but I've tried to >override isReadOnly, and it does not seem to be even called from saveChanges. >I can't make R/O the whole entity: it applies to only some of its objects. I >can't throw from validateForDelete either: I don't want saveChanges to fail. I >need it to work all right with all the other objects, just not deleting a >couple of special ones (nor their owning relationships). > >Thanks, >OC > > > > _______________________________________________ >Do not post admin requests to the list. They will be ignored. >Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) >Help/Unsubscribe/Update your Subscription: >https://lists.apple.com/mailman/options/webobjects-dev/chill%40gevityinc.com > >This email sent to ch...@gevityinc.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
