Mailing-List: contact ddlutils-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ddlutils-dev@db.apache.org
Message-ID: <23620417.55281272451712339.JavaMail.jira@thor>
Date: Wed, 28 Apr 2010 06:48:32 -0400 (EDT)
From: "Tom Palmer (JIRA)" <jira@apache.org>
To: ddlutils-dev@db.apache.org
Subject: [jira] Updated: (DDLUTILS-259) Support splitting the model across
 multiple files
In-Reply-To: <16675985.55241272451593882.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tom Palmer updated DDLUTILS-259:
--------------------------------

    Priority: Minor  (was: Major)

No need for this to be a major issue.

> Support splitting the model across multiple files
> -------------------------------------------------
>
>                 Key: DDLUTILS-259
>                 URL: https://issues.apache.org/jira/browse/DDLUTILS-259
>             Project: DdlUtils
>          Issue Type: New Feature
>          Components: Core (No specific database)
>    Affects Versions: 1.1
>            Reporter: Tom Palmer
>            Assignee: Thomas Dudziak
>            Priority: Minor
>
> The current approach of having the model defined in a single file can be quite limiting on a large model (e.g. working with a large file) and/or a distributed team (e.g. conflicting changes on the same file in svn). Unfortunately the current work-around that the DdlToDatabaseTask uses to initialise individual models and merge them into a master model doesn't work if the model is highly coupled as it might not always be desirable to have all of the related tables in a single file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.