• 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: Do batch faults "cascade" ?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Do batch faults "cascade" ?


  • Subject: Re: Do batch faults "cascade" ?
  • From: Art Isbell <email@hidden>
  • Date: Thu, 11 May 2006 15:45:58 -1000

On May 11, 2006, at 3:19 PM, Chuck Hill wrote:

Batch faulting just ensure that when one fault is fired, others are fired at the same time so that fewer trips are made to the database. prefetchingRelationshipKeyPaths is about pulling in all objects related to the object(s) being fetched.

EODatabaseContext's batchFetchRelationship() efficiently fetches all objects related to an array of objects of a single type in no more than two fetches. This can prevent performance-killing individual fetches as objects related to objects in an array are referenced (e.g., in a WORepetition).


EOF provides a variety of different ways to efficiently fetch objects related to other objects.

Aloha,
Art

_______________________________________________
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: 
 >Do batch faults "cascade" ? (From: Owen McKerrow <email@hidden>)
 >Re: Do batch faults "cascade" ? (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: Do batch faults "cascade" ?
  • Next by Date: Re: Webservice Serializing/Deserializing WOStringKeyMap fails
  • Previous by thread: Re: Do batch faults "cascade" ?
  • Next by thread: Re: Webservice Serializing/Deserializing WOStringKeyMap fails
  • Index(es):
    • Date
    • Thread