db-ddlutils-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Dudziak (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DDLUTILS-89) Add support for ordering of foreign keys when reading from a live database
Date Tue, 18 Jul 2006 07:01:15 GMT
     [ http://issues.apache.org/jira/browse/DDLUTILS-89?page=all ]

Thomas Dudziak resolved DDLUTILS-89.

    Resolution: Fixed

The platform interface has a new property foreignKeysSorted, and the two tasks (DatabaseToDdl,
DdlToDatabase) have a related sortForeignKeys attribute, which - when set to true - force
the alphabetical sorting of the foreign keys of the tables read from the database. Note that
this does not affect the foreign keys of tables read from an XML file.

> Add support for ordering of foreign keys when reading from a live database
> --------------------------------------------------------------------------
>                 Key: DDLUTILS-89
>                 URL: http://issues.apache.org/jira/browse/DDLUTILS-89
>             Project: DdlUtils
>          Issue Type: Improvement
>          Components: Core (No specific database), Ant Tasks
>         Environment: Oracle 10g EE
> SQLServer 2005 EE
> Windows XP SP2
> Java 1.5.0_06
>            Reporter: Guy Davis
>         Assigned To: Thomas Dudziak
>             Fix For: 1.0
>         Attachments: order_fks.patch
> We use the WriteSchemaToFile task to store our applications schema in a file we place
in our Subversion CM tool.  Every time we run this task, it reorders the foreign keys on a
table.  So, for example, if Table A has FKs X, Y, Z then schema.xml file alternates between:
> <table ...>
>    <fk name='X' .../>
>    <fk name='Y' .../>
>    <fk name='Z' .../>
> </table>
> AND 
> <table ...>
>    <fk name='Z' .../>
>    <fk name='Y' .../>
>    <fk name='X' .../>
> </table>
> Notice, that the keys haven't changed between schema dumps, just the ordering of them
in the file.  This means tracking version changes is more complicated as a developer's real
changes are mixed in with these spurious key position changes.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message