Be aware that if you have a two-way relationship where one side is
light, and one side is heavy, i.e.:
user <--->> transactions
You might want to call transaction.setUser(u) over
transaction.setUserRelationship(u), because the relationship call
has to fetch all the transactions for a given user because its not
smart enough to notice that user->transactions() is a fault, so it
can ignore the "add" step for now...
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.
ms
_______________________________________________
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]
