[DDLUTILS-215] Allow custom ModelChanges for altering a database

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.0
• Fix Version/s: 1.3
• Component/s: Core (No specific database)
• Assignee: Thomas Dudziak
• Reporter: Rick Riemer
• Created: 17/Jul/08 12:48
• Updated: 03/Nov/08 22:10

Description

The Platform interface allows for upgrading a database from one model to another using the getAlterModelSql() method. This method tries to automatically convert from one model to another. In some cases it may be useful to allow the caller to provide for the changes that should be processed instead of automatically determining the changes.

I'm attaching a patch that makes the PlatformImplBase.processChanges() method available on the Platform interface, thereby allow the caller to apply a custom list of changes. Next to that, the patch introduces the CustomChange interface, through which the caller can define custom changes (e.g.: executing custom SQL statements).

This patch may also fix #DDLUTILS-213

Issue Links

• is depended upon by: DDLUTILS-218 Introduce table, column, foreign key and index rename changes
• is related to: DDLUTILS-216 Split SqlBuilder.copyData() to allow for copying specific columns
• relates to: DDLUTILS-213 Add ability to execute arbitrary SQL at certain points during database creation/alteration