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 "Hajo Birthelmer (JIRA)" <ji...@apache.org> on 2006/11/30 02:18:21 UTC

[jira] Created: (DDLUTILS-135) mergeWith in Database needs to handle existing tables correctly

mergeWith in Database needs to handle existing tables correctly
---------------------------------------------------------------

                 Key: DDLUTILS-135
                 URL: http://issues.apache.org/jira/browse/DDLUTILS-135
             Project: DdlUtils
          Issue Type: Bug
          Components: Core (No specific database)
    Affects Versions: 1.0
         Environment: MySQL
            Reporter: Hajo Birthelmer
         Assigned To: Thomas Dudziak


mergeWith in Database.java throws a ModelException if the target database already contains a table described in the source (additional) model. 
The correct behavior would compare the existing table and the new description and add columns, keys and indexes to the target if necessary (note that for all practical purposes existing columns/indexes etc. should NOT be removed)


-- 
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

        

[jira] Updated: (DDLUTILS-135) mergeWith in Database needs to handle existing tables correctly

Posted by "Thomas Dudziak (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DDLUTILS-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Dudziak updated DDLUTILS-135:
------------------------------------

    Fix Version/s:     (was: 1.1)
                   1.2

> mergeWith in Database needs to handle existing tables correctly
> ---------------------------------------------------------------
>
>                 Key: DDLUTILS-135
>                 URL: https://issues.apache.org/jira/browse/DDLUTILS-135
>             Project: DdlUtils
>          Issue Type: Bug
>          Components: Core (No specific database)
>    Affects Versions: 1.0
>         Environment: MySQL
>            Reporter: Hajo Birthelmer
>            Assignee: Thomas Dudziak
>             Fix For: 1.2
>
>         Attachments: DdlUtils-135-patch.txt
>
>
> mergeWith in Database.java throws a ModelException if the target database already contains a table described in the source (additional) model. 
> The correct behavior would compare the existing table and the new description and add columns, keys and indexes to the target if necessary (note that for all practical purposes existing columns/indexes etc. should NOT be removed)

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


[jira] Updated: (DDLUTILS-135) mergeWith in Database needs to handle existing tables correctly

Posted by "Hajo Birthelmer (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/DDLUTILS-135?page=all ]

Hajo Birthelmer updated DDLUTILS-135:
-------------------------------------

    Attachment: DdlUtils-135-patch.txt

The attached patch contains a table-merge logic that allows two tables to be compared for columns,foreign keys and indexes and adds missing elements to the target. 

> mergeWith in Database needs to handle existing tables correctly
> ---------------------------------------------------------------
>
>                 Key: DDLUTILS-135
>                 URL: http://issues.apache.org/jira/browse/DDLUTILS-135
>             Project: DdlUtils
>          Issue Type: Bug
>          Components: Core (No specific database)
>    Affects Versions: 1.0
>         Environment: MySQL
>            Reporter: Hajo Birthelmer
>         Assigned To: Thomas Dudziak
>         Attachments: DdlUtils-135-patch.txt
>
>
> mergeWith in Database.java throws a ModelException if the target database already contains a table described in the source (additional) model. 
> The correct behavior would compare the existing table and the new description and add columns, keys and indexes to the target if necessary (note that for all practical purposes existing columns/indexes etc. should NOT be removed)

-- 
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

        

[jira] Updated: (DDLUTILS-135) mergeWith in Database needs to handle existing tables correctly

Posted by "Thomas Dudziak (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/DDLUTILS-135?page=all ]

Thomas Dudziak updated DDLUTILS-135:
------------------------------------

    Fix Version/s: 1.1

> mergeWith in Database needs to handle existing tables correctly
> ---------------------------------------------------------------
>
>                 Key: DDLUTILS-135
>                 URL: http://issues.apache.org/jira/browse/DDLUTILS-135
>             Project: DdlUtils
>          Issue Type: Bug
>          Components: Core (No specific database)
>    Affects Versions: 1.0
>         Environment: MySQL
>            Reporter: Hajo Birthelmer
>         Assigned To: Thomas Dudziak
>             Fix For: 1.1
>
>         Attachments: DdlUtils-135-patch.txt
>
>
> mergeWith in Database.java throws a ModelException if the target database already contains a table described in the source (additional) model. 
> The correct behavior would compare the existing table and the new description and add columns, keys and indexes to the target if necessary (note that for all practical purposes existing columns/indexes etc. should NOT be removed)

-- 
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