[ 
https://issues.apache.org/jira/browse/TORQUE-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Fox closed TORQUE-183.
-----------------------------

    
> allow for large schemas to be broken up into sub-schema files
> -------------------------------------------------------------
>
>                 Key: TORQUE-183
>                 URL: https://issues.apache.org/jira/browse/TORQUE-183
>             Project: Torque
>          Issue Type: Wish
>          Components: Generator
>    Affects Versions: 3.3.1
>            Reporter: Helge Weissig
>            Assignee: Thomas Fox
>             Fix For: 4.0-beta1
>
>
> In an attempt to break up a large schema file into smaller sub-schema files 
> using the external schema feature, I recently ran into a design feature with 
> the torque generator and the implementation of the complexDataModel flag.
> To illustrate, I have created a github project at 
> https://github.com/helgew/Torque-Schema-Test. As you will see, there are two 
> schema files: first-schema.xml (defines tbl1) and second-schema.xml (defines 
> tbl2 and tbl3) which includes the first. The second file defines a link table 
> between tbl2 and tbl1 as well as tbl3 respectively. The generated base 
> classes for tbl1 and tbl3 differ in that BaseTbl3 has the getter methods for 
> the link table, whereas BaseTbl1 does not.
> As was pointed out to me on the mailing list, this behavior is intended. 
> However, 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!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to