[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Java Packages for Dummies

Subject: Re: Java Packages for Dummies
From: Mike Schrag <email@hidden>
Date: Tue, 4 Dec 2007 19:33:38 -0500
Delivered-to: email@hidden
Delivered-to: email@hidden

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@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/email@hidden

This email sent to email@hidden

Follow-Ups:
- Re: Java Packages for Dummies
  - From: David Avendasora <email@hidden>

References:
	>Java Packages for Dummies (From: Owen McKerrow <email@hidden>)
	>Re: Java Packages for Dummies (From: Chuck Hill <email@hidden>)
	>Re: Java Packages for Dummies (From: Owen McKerrow <email@hidden>)
	>Re: Java Packages for Dummies (From: "Pierce T. Wetter III" <email@hidden>)

Prev by Date: Re: OT : Steve Jobs Interviewed about WebObjects
Next by Date: ExistsInRelationshipQualifier
Previous by thread: Re: Java Packages for Dummies
Next by thread: Re: Java Packages for Dummies
Index(es):
- Date
- Thread

Home