Hi Helge,
> I just ran into what may be a feature or a bug... trying to find
> out which: When I define a table in schema1.xml and another two,
> including a link table for a many-to-many relationship in
> schema2.xml, where schema2.xml includes schema1.xml as an external
> schema, torque will not generated the getter methods for the foreign
keys.
This behaviour is by design. I was not around when this decision was made
but the idea is that a "external" schema is references which has no
knowledge of the referencing schema.
> To illustrate, I have created a github project. As you will see,
> there are two schema files: first-schema.xml and second-schema.xml
> which includes the first. The generated base classes for tbl1 and
> tbl3 differ in that BaseTbl3 has the getter methods for the link
> table tbl_link_int (e.g. getTblLinkInts()), whereas BaseTbl1 does not.
>
> I think it would be a very useful feature to be able to split a
> large schema into several sub-schema files and not lose the ability
> to generate these setters! Maybe I am doing something wrong though!?
This would be a different feature. Something like <import-schema.... />
You can create a jira issue for it. Personally I regard this as a sueful
feature so there is a good probability that it will be implemented for
Torque 4.
Cheers,
Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscr...@db.apache.org
For additional commands, e-mail: torque-user-h...@db.apache.org
