Mailing-List: contact ddlutils-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ddlutils-dev@db.apache.org
Message-ID: <1665937654.1216298971604.JavaMail.jira@brutus>
Date: Thu, 17 Jul 2008 05:49:31 -0700 (PDT)
From: "Rick Riemer (JIRA)" <jira@apache.org>
To: ddlutils-dev@db.apache.org
Subject: [jira] Created: (DDLUTILS-215) Allow custom ModelChanges for
 altering a database
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Allow custom ModelChanges for altering a database
-------------------------------------------------

                 Key: DDLUTILS-215
                 URL: https://issues.apache.org/jira/browse/DDLUTILS-215
             Project: DdlUtils
          Issue Type: Improvement
          Components: Core (No specific database)
    Affects Versions: 1.0
            Reporter: Rick Riemer
            Assignee: Thomas Dudziak
             Fix For: 1.1


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

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