Re: Back To Basics : Databases Active Editing Context
Re: Back To Basics : Databases Active Editing Context
- Subject: Re: Back To Basics : Databases Active Editing Context
- From: Lachlan Deck <email@hidden>
- Date: Fri, 4 Jul 2008 13:00:49 +1000
On 04/07/2008, at 11:54 AM, Chuck Hill wrote:
On Jul 3, 2008, at 6:37 PM, M.Y. Tjoe wrote:
Hi Chunk and Owen,
Chunk?
Might be colloquial for something down in Wollongong or maybe
something from that 3rd world you mentioned before ;-)
On 04/07/2008, at 9:53 AM, Chuck Hill wrote:
If not what does lock() on the EC actually lock ?
It prevents changes in other ECs from affecting what is happening
in the locked EC. The changes are queued and processed when the
EC is unlocked.
If so, shouldn't rest of EC (waiting to save changes) just hang
around and wait instead of trying to access DBcontext and throw
exception? In other words, the exception we are seeing implies that
rest of ECs have no idea there is ec out there locked the DBcontext.
No, that is just a badly worded exception. What it really means is
Called objectForGlobalID() on the databaseContext's active
editingContext,
edu.uow.ris.framework.LockErrorScreamerEditingContext@1efaa51, and
got back null. The object
: Researcher:(Active_Name=Peter Newnam {rowID=28082;}, is in editing
context
edu.uow.ris.framework.LockErrorScreamerEditingContext@10c6406.
I've seen this happen when attempting to localize an object into
another ec fails... and you find out when attempting to save changes.
e.g., using some context that wasn't properly locked.
with regards,
--
Lachlan Deck
_______________________________________________
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