• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Yes, even one more concurrency question - relationship "freshness"
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Yes, even one more concurrency question - relationship "freshness"


  • Subject: Re: Yes, even one more concurrency question - relationship "freshness"
  • From: Miguel Arroz <email@hidden>
  • Date: Tue, 14 Aug 2007 22:23:15 +0100

Hi!

On 2007/08/14, at 17:40, Chuck Hill wrote:

See, it is trying to create an UPDATE statement for this object. Something has trashed the EC state.

Maybe try adding
ec.undoManager().removeAllActions(); before the call to saveChanges (), or try getting rid of the undo manager before making any changes:


ec.setUndoManager(null);

If you are not reverting, you don't need this.

Hmmm, I have some recollection than an exception thrown during the delete processing of saveChanges() trashing EC state. IIRC, it was undo manager related. I have an EC subclass that calls ec.undoManager().removeAllActions(); after each successful save to avoid this problem. So this might be close to what is happening to you.

Tried both (the setUndoManager(null) and removeAllActions()) and it still doesn't work. I give up. Going to rewrite this using the technique I described earlier.


  Yours

Miguel Arroz

Miguel Arroz
http://www.terminalapp.net
http://www.ipragma.com



_______________________________________________
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


References: 
 >Yes, even one more concurrency question - relationship "freshness" (From: Miguel Arroz <email@hidden>)
 >Re: Yes, even one more concurrency question - relationship "freshness" (From: Chuck Hill <email@hidden>)
 >Re: Yes, even one more concurrency question - relationship "freshness" (From: Miguel Arroz <email@hidden>)
 >Re: Yes, even one more concurrency question - relationship "freshness" (From: Chuck Hill <email@hidden>)
 >Re: Yes, even one more concurrency question - relationship "freshness" (From: Miguel Arroz <email@hidden>)
 >Re: Yes, even one more concurrency question - relationship "freshness" (From: Chuck Hill <email@hidden>)
 >Re: Yes, even one more concurrency question - relationship "freshness" (From: Miguel Arroz <email@hidden>)
 >Re: Yes, even one more concurrency question - relationship "freshness" (From: Chuck Hill <email@hidden>)
 >Re: Yes, even one more concurrency question - relationship "freshness" (From: Miguel Arroz <email@hidden>)
 >Re: Yes, even one more concurrency question - relationship "freshness" (From: Chuck Hill <email@hidden>)
 >Re: Yes, even one more concurrency question - relationship "freshness" (From: Miguel Arroz <email@hidden>)
 >Re: Yes, even one more concurrency question - relationship "freshness" (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: Yes, even one more concurrency question - relationship "freshness"
  • Next by Date: Re: Common application for different database users
  • Previous by thread: Re: Yes, even one more concurrency question - relationship "freshness"
  • Next by thread: Proxied Scripting
  • Index(es):
    • Date
    • Thread