Usually you would not have a docpatients
destination unless you needed to store additional info on that mapping (like
the date the doctor acquired that patient). Usually the docpatient table only
has the doctor-id and patient-id and nothing else. If it has other info, then
you might need the extra Java object and then an extra destination to model the
“mapping class”. Assuming you don’t need the mapping object,
if doctor has a “patients” property and patient has a “doctors”
property it should look like: For destination doctor: <many-to-many property=”patients”
destination=”app.medical.patient” lazy=”true”/> For destination patient: <many-to-many property=”doctors”
destination=”app.medical.doctor” lazy=”true”/> The choice as to whether you use lazy=”true”
or false on FDMS is independent of whether you use lazy=true/false in hibernate
(note that hibernate defaults to lazy=”true” but FDMS defaults the
other way around). Hibernate’s lazy property controls how objects are
fetched from SQL, FDMS controls how the client fetches objects from the server.
I recommend starting off with lazy=”true” and then turning it to
false when you find you need the performance or if the “ItemPendingErrors”
cause you problems on the client when you try to fetch an item which is not
loaded. Jeff From:
flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of passive_thoughts Can anyone provide an example of what the metadata
section of my -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required) Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe __,_._,___ |
- RE: [flexcoders] many-to-many destinations help Jeff Vroom
- [flexcoders] Re: many-to-many destinations help passive_thoughts