I think this is a key "best practice". It is something that I
struggled with for a while, while trying to figure out why my
application was so slow. It's logical to add both relationships, but
once you understand what is happening, it is logical to leave the
heavy relationship off and use a Fetch Specification instead.
Looks like the Best Practices portion of the Wiki would use a little
work. I'll try to get to it later today...
Dave
On Dec 4, 2007, at 7:33 PM, Mike Schrag wrote:
I prefer not modeling the inverse relationship in these cases. The
problem is that if the heavy side has already faulted, it will now
just be out of sync, so if you DO have to get the results from it,
it won't contain your recent update. So I usually don't model the
heavy relationship and instead write the equivalent cover methods
on the Java class that just fetch them with a fetch spec so they're
always fresh.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
