[DDLUTILS-176] Prevent the deletion of changes made to a database when generating the alter script from the API

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

Description

When using the model to alter the source database, the scripts or the database commands issued will change the source in such a way that it will match exactly, the target database. This patch will allow the user the option of not including commands to drop tables, indicies, identity columns, required fields or longer fields that a user may have made to a database. The target database will then be the minimum requirements that a database must meet and later commands will be generated to add missing tables, columns or properties to the columns.

Issue Links

• is part of: DDLUTILS-182 New flags for ForeignKeys, index names and dropping tables
• is related to: DDLUTILS-5 I'm unable to specify that i don't want any sql drops generated with WriteSchemaSqlToFileCommand
• is related to: DDLUTILS-91 writeSchemaSqlToFile could write the 'drops' and the 'creates' commands in separated files.