• 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: Alan Ward <email@hidden>
  • Date: Fri, 30 May 2008 14:31:15 -0600


I'm actually somewhat opposed to flattening in any situation but when it comes to M-to-M
my justification is more performance related than anything else. 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. If you're working with a small data set then none of this is
a big deal but once you get up into 10's of millions of rows in any given table then you have
to be extremely careful with the modeling in order to avoid unexpected killer fetches.


You know what I work on and I think our challenges are somewhat atypical. I do believe though
that they have some value as general principals because however small your data set is
to begin with, it likely will grow over time.


Alan

On May 30, 2008, at 2:19 PM, Mike Schrag wrote:

IMHO you should never flatten a many-to-many (especially across models).
So this is interesting ... I held this same belief for years until about 6 months ago when Chuck convinced me that I was missing out :) I had some silly misunderstanding of EOF caching with respect to flattened relationships that Chuck proved was wrong. I've since been pretty happy with them (though admittedly I've never crossed model boundaries). I'm curious what you're reasoning for not flattening is? Definitely it will fail across databases boundaries (which totally makes sense), but it's not immediately obvious that (or rather why) it would fail across model boundaries onto the same database (assuming you have the EXACT same connection dictionary between the two).

ms

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.com


This email sent to email@hidden

_______________________________________________ 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: Guido Neitzer <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>)

  • 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