> 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 !
As Leon said, adding these types of features would be pushing it in that
direction, and we may not want that. Also, consider if the relationship is
"0 or 1 to many" where for example a Contact may or may not have a
BusinessType specified. Then the BusinessType would have to come from
either an outer join, or a separate query. This is an additional
complication to what I described earlier.
> 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.
>
Again, I don't think that Torque can auto-generate that, but you can take
what it does generate, and cut and paste it to get what you want.
-Nissim
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
