On Apr 19, 2007, at 9:45 AM, Steven Mark McCraw wrote:

Hi all,

I've been working all morning trying to debug cryptic EOF exceptions, and as per the usual with that, am getting nowhere. I can almost replicate some of them, but the behavior is inconsistent and therefore very frustrating. Almost all of them seem to hinge in some way or other on EODatabaseContext whining about its snapshot. Either it can't find a snapshot for an EO that is being deleted, or it can't decrement a snapshot count (that doesn't exist or is already zero), or there is no snapshot available for some object when it is trying to save changes. I am obviously doing something wrong, although I can't figure out where to look. I think it would be extremely helpful in tracking down the issue if there were some way to be able to examine the snapshot of the EODatabaseContext for session().defaultEditingContex().

The snapshots are per-EO and shared between editing contexts.


I'm guessing (based on the existence of the method EODatabaseContext.localSnapshotForGlobalID(...)) that when the Apple documentation vaguely rambles on and on about the "snapshot" that what they're really talking about is an NSMutableDictionary keyed on a EOGlobalID whose values are NSDictionaries mapping attribute names to values for Enterprise Objects.

Yes.


Is there some way to just get this overall dictionary so that I can print it out as I go to see where things are getting off track? Am I taking the right approach here? Any advice would be appreciated.

ec.committedSnapshotForObject(eo);


Chuck

--

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects





_______________________________________________
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]

Reply via email to