• 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: Relationship across model boundaries failing
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Relationship across model boundaries failing


  • Subject: Re: Relationship across model boundaries failing
  • From: Chuck Hill <email@hidden>
  • Date: Fri, 30 May 2008 14:45:11 -0700


On May 30, 2008, at 1:59 PM, Alan Ward wrote:


I'm sure Chuck will correct me if I'm wrong but my recollection is that a flattened to-many will always trip on an
insert or update.

Any to many, flattened or not, will fire the array fault (but not fire the faults in the array) when an element is added to or removed from the relationship. I can't think of how flattening would affect this. You should see the exact same SQL. Now it _would_ be nice if EOF could just add / remove and mark the snapshot as partial or something to avoid this overhead.


Chuck


On May 30, 2008, at 2:48 PM, Guido Neitzer wrote:

On 30.05.2008, at 14:31, Alan Ward wrote:

I actually omit joins from the model in certain situations to avoid unwanted fetches and flattening is more of a recipe for disaster than a simple join is.


But it actually doesn't matter how big your datasets are. The interesting question is how big the joins are. I have a database here with some ten million entries in it and the biggest to-many is a couple of hundred objects - this runs on a dual G4 with a small disk array and never gave me any problems.

And I rather have the development speed of flattened relationships and working to-many relationships and deal with the consequences when I have to. Yes, I had to turn of some back-relationships over time and do not model some of the inverse relationships at all, because I know they will cause problems, but as an overall rule? No, definitely not.

cug

--
http://www.event-s.net


_______________________________________________ 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


--

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@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Relationship across model boundaries failing
      • From: Mike Schrag <email@hidden>
References: 
 >Relationship across model boundaries failing (From: Juergen Lorenz Simon <email@hidden>)
 >Fwd: Relationship across model boundaries failing (From: "Gennady Kushnir" <email@hidden>)
 >Re: Relationship across model boundaries failing (From: Alan Ward <email@hidden>)
 >Re: Relationship across model boundaries failing (From: Mike Schrag <email@hidden>)
 >Re: Relationship across model boundaries failing (From: Alan Ward <email@hidden>)
 >Re: Relationship across model boundaries failing (From: Guido Neitzer <email@hidden>)
 >Re: Relationship across model boundaries failing (From: Alan Ward <email@hidden>)

  • Prev by Date: Re: Relationship across model boundaries failing
  • Next by Date: Re: Relationship across model boundaries failing
  • Previous by thread: Re: Relationship across model boundaries failing
  • Next by thread: Re: Relationship across model boundaries failing
  • Index(es):
    • Date
    • Thread