On Aug 13, 2008, at 8:16 PM, Lachlan Deck wrote:
On 14/08/2008, at 12:25 PM, Dov Rosenberg wrote:
In our case we create a new EC because we use a SharedEC for read
only data.
Is the shared ec locked for reading or writing?
When we need to modify an object we create a new EC and set the
reference to
the SharedEC to null and rely on the Object Store Coordinator to
notify the
SharedEC when the change is committed. We need objects from the
SharedEC so
we use LocalInstance to get one.
Yep.
We have fixed other similar issues by just refetching the objects
into a new EditingContext instead of using localInstance.
I would expect that to be far, far slower.
Have you tried just faulting from the global ids of the objects?
Which is exactly what localInstance does:
public static EOEnterpriseObject
localInstanceOfObject(EOEditingContext ec, EOEnterpriseObject object) {
// Edited for clarity
EOGlobalID globalID =
object.editingContext().globalIDForObject(object);
return ec.faultForGlobalID(globalID, ec);
}
--
Chuck Hill Senior Consultant / VP Development
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]
