Return-Path: 
 <torque-dev-return-10912-apmail-db-torque-dev-archive=db.apache.org@db.apache.org>
X-Original-To: apmail-db-torque-dev-archive@www.apache.org
Delivered-To: apmail-db-torque-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 57DC79D2E
	for <apmail-db-torque-dev-archive@www.apache.org>;
 Thu, 12 Apr 2012 01:40:38 +0000 (UTC)
Received: (qmail 48593 invoked by uid 500); 12 Apr 2012 01:40:38 -0000
Delivered-To: apmail-db-torque-dev-archive@db.apache.org
Received: (qmail 48540 invoked by uid 500); 12 Apr 2012 01:40:38 -0000
Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:torque-dev-unsubscribe@db.apache.org>
List-Help: <mailto:torque-dev-help@db.apache.org>
List-Post: <mailto:torque-dev@db.apache.org>
List-Id: "Apache Torque Developers List" <torque-dev.db.apache.org>
Reply-To: "Apache Torque Developers List" <torque-dev@db.apache.org>
Delivered-To: mailing list torque-dev@db.apache.org
Received: (qmail 48532 invoked by uid 99); 12 Apr 2012 01:40:38 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Apr 2012 01:40:38 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Apr 2012 01:40:37 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 099C3366325
	for <torque-dev@db.apache.org>; Thu, 12 Apr 2012 01:40:17 +0000 (UTC)
Date: Thu, 12 Apr 2012 01:40:17 +0000 (UTC)
From: "Thomas Fox (Resolved) (JIRA)" <jira@apache.org>
To: torque-dev@db.apache.org
Message-ID: 
 <2034625408.15741.1334194817040.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1259625995.3020.1330524238913.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (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: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


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

Thomas Fox resolved TORQUE-183.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 4.0
         Assignee: Thomas Fox

You can now use an <include-schema file="..." /> element to include other files as if they were part of the original schema.
Take care to exclude the included files from generation, otherwise Torque may complain about not being able to resolve foreign key relations.
                
> 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
>
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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