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 "Brian Devaney (JIRA)" <ji...@apache.org> on 2007/08/20 21:03:31 UTC
[jira] Created: (DDLUTILS-182) New flags for ForeignKeys, index
names and dropping tables
New flags for ForeignKeys, index names and dropping tables
----------------------------------------------------------
Key: DDLUTILS-182
URL: https://issues.apache.org/jira/browse/DDLUTILS-182
Project: DdlUtils
Issue Type: Improvement
Components: Core (No specific database)
Reporter: Brian Devaney
Assignee: Thomas Dudziak
Priority: Minor
This patch contains changes for issues in DdlUtils-176 and DdlUtils-177. The main addition was to provide a flag that would change checking for the names of foreign keys or the names of indexes when comparing the two. For foreign keys, if the PlatformImplBase.setForeignKeyNameMatters is set to false, and tables were the same and the columns indexed were the same, then the foreign keys would be considered the same. Similarly, for Indexes, id the PlatformImplBase.setIndexNameMatters is set to false, then if the columns match and are in the same order, then the index is considered the same. Both these flags default to true to preserve how the code operated now.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DDLUTILS-182) New flags for ForeignKeys, index
names and dropping tables
Posted by "Brian Devaney (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DDLUTILS-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Devaney updated DDLUTILS-182:
-----------------------------------
Attachment: ForeignKeyNameMatters.patch
This contains fixes for other related issues in DdlUtils
> New flags for ForeignKeys, index names and dropping tables
> ----------------------------------------------------------
>
> Key: DDLUTILS-182
> URL: https://issues.apache.org/jira/browse/DDLUTILS-182
> Project: DdlUtils
> Issue Type: Improvement
> Components: Core (No specific database)
> Reporter: Brian Devaney
> Assignee: Thomas Dudziak
> Priority: Minor
> Attachments: ForeignKeyNameMatters.patch
>
>
> This patch contains changes for issues in DdlUtils-176 and DdlUtils-177. The main addition was to provide a flag that would change checking for the names of foreign keys or the names of indexes when comparing the two. For foreign keys, if the PlatformImplBase.setForeignKeyNameMatters is set to false, and tables were the same and the columns indexed were the same, then the foreign keys would be considered the same. Similarly, for Indexes, id the PlatformImplBase.setIndexNameMatters is set to false, then if the columns match and are in the same order, then the index is considered the same. Both these flags default to true to preserve how the code operated now.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DDLUTILS-182) New flags for ForeignKeys, index
names and dropping tables
Posted by "Thomas Dudziak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DDLUTILS-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Dudziak updated DDLUTILS-182:
------------------------------------
Fix Version/s: 1.1
> New flags for ForeignKeys, index names and dropping tables
> ----------------------------------------------------------
>
> Key: DDLUTILS-182
> URL: https://issues.apache.org/jira/browse/DDLUTILS-182
> Project: DdlUtils
> Issue Type: Improvement
> Components: Core (No specific database)
> Reporter: Brian Devaney
> Assignee: Thomas Dudziak
> Priority: Minor
> Fix For: 1.1
>
> Attachments: ForeignKeyNameMatters.patch
>
>
> This patch contains changes for issues in DdlUtils-176 and DdlUtils-177. The main addition was to provide a flag that would change checking for the names of foreign keys or the names of indexes when comparing the two. For foreign keys, if the PlatformImplBase.setForeignKeyNameMatters is set to false, and tables were the same and the columns indexed were the same, then the foreign keys would be considered the same. Similarly, for Indexes, id the PlatformImplBase.setIndexNameMatters is set to false, then if the columns match and are in the same order, then the index is considered the same. Both these flags default to true to preserve how the code operated now.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.