[DDLUTILS-182] New flags for ForeignKeys, index names and dropping tables

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Fix Version/s: 1.3
• Component/s: Core (No specific database)
• Assignee: Thomas Dudziak
• Reporter: Brian Devaney
• Created: 20/Aug/07 19:03
• Updated: 03/Nov/08 22:10

Description

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.

Issue Links

• blocks: DDLUTILS-177 Table does not have a getRequiredColumns method
• incorporates: DDLUTILS-176 Prevent the deletion of changes made to a database when generating the alter script from the API