Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Developers List" <torque-dev@db.apache.org>
Date: Wed, 29 Feb 2012 14:11:56 +0000 (UTC)
From: "Helge Weissig (Updated) (JIRA)" <jira@apache.org>
To: torque-dev@db.apache.org
Message-ID: 
 <1199276794.3048.1330524716896.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1259625995.3020.1330524238913.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (TORQUE-183) allow for large schemas to be broken
 up into sub-schema files
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/TORQUE-183?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Helge Weissig updated TORQUE-183:
---------------------------------

    Description:=20
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 wi=
th 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-sch=
ema.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 t=
bl1 as well as tbl3 respectively. The generated base classes for tbl1 and t=
bl3 differ in that BaseTbl3 has the getter methods for the link table, wher=
eas BaseTbl1 does not.

As was pointed out to me on the mailing list, this behavior is intended. Ho=
wever, I think it would be a very useful feature to be able to split a larg=
e schema into several sub-schema files and not lose the ability to generate=
 these setters!

  was:
In an attempt to break up a large schema file into smaller sub-schema files=
, I recently ran into a design feature with [torque|http://db.apache.org/to=
rque], external schemas, and the implementation of the complexDataModel fla=
g.

To illustrate, I have created [a github project|https://github.com/helgew/T=
orque-Schema-Test]. As you will see, there are two schema files: [first-sch=
ema.xml|https://github.com/helgew/Torque-Schema-Test/blob/master/src/main/t=
orque/schema/first-schema.xml] and [second-schema.xml|https://github.com/he=
lgew/Torque-Schema-Test/blob/master/src/main/torque/schema/second-schema.xm=
l] which includes the first. The [generated base classes|https://github.com=
/helgew/Torque-Schema-Test/tree/master/target/generated-sources/torque/org/=
grajagan] for tbl1 and tbl3 differ in that [BaseTbl3|https://github.com/hel=
gew/Torque-Schema-Test/blob/master/target/generated-sources/torque/org/graj=
agan/BaseTbl3.java] has the getter methods for the link table tbl_link_int =
(e.g. [getTblLinkInts()|https://github.com/helgew/Torque-Schema-Test/blob/m=
aster/target/generated-sources/torque/org/grajagan/BaseTbl3.java#L168]), wh=
ereas [BaseTbl1|https://github.com/helgew/Torque-Schema-Test/blob/master/ta=
rget/generated-sources/torque/org/grajagan/BaseTbl1.java] does not.

I think it would be a very useful feature to be able to split a large schem=
a into several sub-schema files and not lose the ability to generate these =
setters!

   =20
> 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
>
> In an attempt to break up a large schema file into smaller sub-schema fil=
es using the external schema feature, I recently ran into a design feature =
with the torque generator and the implementation of the complexDataModel fl=
ag.
> To illustrate, I have created a github project at https://github.com/helg=
ew/Torque-Schema-Test. As you will see, there are two schema files: first-s=
chema.xml (defines tbl1) and second-schema.xml (defines tbl2 and tbl3) whic=
h 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, wh=
ereas 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 la=
rge schema into several sub-schema files and not lose the ability to genera=
te these setters!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org