Re: SharedEditingContext Write Locks?
Re: SharedEditingContext Write Locks?
- Subject: Re: SharedEditingContext Write Locks?
- From: Dov Rosenberg <email@hidden>
- Date: Mon, 14 Nov 2005 21:20:50 -0500
- Thread-topic: SharedEditingContext Write Locks?
We took a closer look at our code and made some changes. We were using a
method out of EOUtilities to get data instead of using
objectsWithFetchSpecification. Hopefully that will clear up our issue. I
will let everyone know if that works.
A point of clarification:
Based on one of the links that someone sent along, it seems like the
SharedEditingContext should never be passed into a method to do a fetch
unless objectsWithFetchSpecification is used. It seems that
objectsWithFetchSpecification is used to load the SEC, I am not sure why I
would use objectsByEntityName or
objectsByEntityNameAndFetchSpecificationName. It seems that these methods
could return a huge number of objects. Is the idea that you could filter the
Shared objects in memory like you would in the DB?
Thanks again
Dov Rosenberg
_______________________________________________
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