>The main difficulty I can see for generalizing this is if the Class
>contains
>many related classes. Maybe each generated class which is the many side of
>a 1 to many relationship should have a doSelectRelated which puts in all
>the
>joins for getting the related classes. And the class which is the 1 side of
>the 1 to many relationship would have a method void loadXXX which would
>load
>the Vector of related objects. Then there could be a tag in the XML which
>would specify whether the loadXXX methods should be called when the objects
>are created.
>
>What do you think of that?
For myself, that seems good and even great ! - Your solution solves the
issue concerning the object associations (1 to many). If you continue like
this, Torque will become a 4GL ;) but now ! What is the Peer design if 2
tables are using for the same class (1 to 1 relation). For example, a
customer has a 'employee entity' split into 2 tables. some applications are
using both tables and other applications that require minimum employee
information use only one table. Do you think that is possible to map these
tables to the same Peer class and also used Torque for that ? It is
certainly another 'getting started' question but I didn't see something in
the doc's.
Christophe
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Share information about yourself, create your own public profile at
http://profiles.msn.com.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
