Re: back relationships
Re: back relationships
- Subject: Re: back relationships
- From: Art Isbell <email@hidden>
- Date: Mon, 24 May 2004 08:21:46 -1000
On May 24, 2004, at 4:33 AM, John Spicer wrote:
When constructing a relationship with EOModeler, either a one to one
or one to many, the modeler automatically creates a back relationship,
usually a one to one as well.
Is there a good reason either to delete these or keep them? Is there a
super advantage to keeping them, or super problems removing them?
I have seen inverse relationship pairs that are both class properties
result in database accesses that I don't feel are necessary for my
application. I suspect that these fetches are required to keep the
object graph consistent with respect to both inverse relationships.
But if my application doesn't ever access one of the inverse
relationship pairs, then I don't care if that relationship's objects
are in sync with the DB.
So I typically define both inverse relationships in my eomodels
because EOF might need both of them for doing its thang (although I
think EOF will try to construct an inverse relationship if one isn't
defined). But I make only one of them a class property. Which one I
make a class property depends on what my application needs to do.
Usually, using one of these relationships makes coding more convenient.
Aloha,
Art
_______________________________________________
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.