You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ddlutils-dev@db.apache.org by "Tom Palmer (JIRA)" <ji...@apache.org> on 2010/04/28 12:46:33 UTC
[jira] Created: (DDLUTILS-259) Support splitting the model across
multiple files
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
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.
[jira] Updated: (DDLUTILS-259) Support splitting the model across
multiple files
Posted by "Tom Palmer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DDLUTILS-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Palmer updated DDLUTILS-259:
--------------------------------
Attachment: modelinmultiplefiles.patch
Attached is a patch to DatabaseIO that will allow a List of Readers to be passed in to create the model from. Because the model initialisation is deferred until all of the readers have been consumed it's possible to define each table in a single file with the referential integrity between tables being maintained.
> 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
> Attachments: modelinmultiplefiles.patch
>
>
> 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.
[jira] Updated: (DDLUTILS-259) Support splitting the model across
multiple files
Posted by "Tom Palmer (JIRA)" <ji...@apache.org>.
[ 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.