“mightDelete()” to remember
“didDelete()” to act
AARON ROSENZWEIG / Chat 'n Bike <http://www.chatnbike.com/>
e:  aa...@chatnbike.com <mailto:aa...@chatnbike.com>  t:  (301) 956-2319        
        
        

> On Jun 15, 2020, at 6:14 AM, OCsite via Webobjects-dev 
> <webobjects-dev@lists.apple.com> wrote:
> 
> Hi there,
> 
> I've just bumped into another problem which seems it should be pretty common, 
> but I can't see a decent solution (due to my blindness quite probably).
> 
> I am caching some information for EOs; the info is EC-independent, and 
> therefore the cache is keyed by global IDs.
> 
> When an EO is successfully deleted, I want to remove the info from the cache. 
> Thus, the cache observes EditingContextDidSaveChangesNotification and would 
> remove the userInfo[EOObjectStore.DeletedKey] objects.
> 
> The problem is that these objects are already unregistered from the EC and I 
> can't get their GIDs anymore.
> 
> Is there a decent known solution of this problem? I probably can do something 
> like storing GIDs of objects which are only being deleted somewhere and use 
> these stored GIDs later when the deletion succeeds, but that seems to be 
> rather at the complex and awkward side for a conceptually simple operation. 
> Do I overlook some simpler solution, or is this indeed the only way?
> 
> 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/aaron%40chatnbike.com
> 
> This email sent to aa...@chatnbike.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

Reply via email to