Re: Invalidating Objects
Re: Invalidating Objects
- Subject: Re: Invalidating Objects
- From: Ramsey Gurley <email@hidden>
- Date: Thu, 20 May 2010 10:57:06 -0400
On May 18, 2010, at 5:24 PM, Andrew Lindesay wrote:
Hello;
As part of a built-in "change notification" facility, I am using
"EOObjectStoreCoordinator.invalidateObjectsWithGlobalIDs(..)" with
the relevant OSC locked. All use of other editing contexts are
locked and unlocked correctly. Occasionally I seem to end up with
"disappearing snapshots" where all the values of the snapshot go to
NULL -- I can only imagine this would be linked to my use of
'invalidate..'. Other new editing contexts then see the NULLed-out
EO and the EO does not seem to re-fault in that instance. When that
"corrupted" EO is used in some sort of qualifier, EOF will treat the
"primary-key qualifier" as looking for NULL.
Any ideas where to look or has anybody else had this problem and has
any pointers?
cheers.
___
Andrew Lindesay
www.silvereye.co.nz
Hi Andrew!
I've seen similar problems, but I don't think it was related to
invalidating objects. It appeared related to the use of nested
editing contexts. There was a discussion about it around two months
ago...
http://www.mail-archive.com/email@hidden/msg36101.html
Using a nested editing context anywhere?
Ramsey
_______________________________________________
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