Jon Stevens wrote:
>
> on 1/2/2001 2:03 PM, "Mike Haberman" <[EMAIL PROTECTED]> wrote:
>
> > I do a select on a table, one of it's fields is a pkey into another table.
> > I then set up a hashtable for the secondtable so that the template
> > writer can get the reference:
>
> This is good, but I think that we need to make sure that we have a more
> complete solution. I feel that this will lead us down a hackdom path.
>
> In other words, essentially, you want to encapsulate some of the business
> logic of the application into the schema.xml file. I think that this is a
> good thing.
>
> So, you have a schema that looks like this:
>
> <table name="movies">
> <column name="movietypeid"/>
>
> <foreign-key foreigntable="movietypes">
> <reference local="movietypeid" foreign="movietypeid"/>
> </foreign-key>
> </table>
>
> Given that you know that movietypeid is a FK, you already know that the
> movietypeid column references another table. I'm not sure why you would need
> to add another column type to figure that out. We should generate the
> get/set code for all of the times we have this case.
We are generating code like this. It is optional, set
objectModel=complex in torque.props.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
