• 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: To Many Fault and Locking
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: To Many Fault and Locking


  • Subject: Re: To Many Fault and Locking
  • From: Arturo PĂ©rez <email@hidden>
  • Date: Sun, 16 May 2004 21:03:30 -0400

On May 16, 2004, at 4:19 PM, Hunter Hillegas wrote:

Later on in the same component, I call restaurants().count(). This triggers all of the locking exceptions, as at that point the EC that the object is in has been unlocked...

Is there a good reason for not having the ec locked at that point? Seems odd if this is all happening within the same request-response loop.


So... Is the best thing to do here to fire that fault before I unlock the EC, right after I do the fetch?

I think you could set the relationship to prefetch. Then you won't have to worry about the faults. But who knows what else those locks are protecting against.


----
WO in philadelphia - wanna cheesesteak with that?
Please visit webobjects.meetup.com.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.


References: 
 >To Many Fault and Locking (From: Hunter Hillegas <email@hidden>)

  • Prev by Date: Off Topic : WWDC Birds of Feather
  • Next by Date: new list member intro
  • Previous by thread: To Many Fault and Locking
  • Next by thread: Re: To Many Fault and Locking
  • Index(es):
    • Date
    • Thread