On 1/29/07, Jun Li <[EMAIL PROTECTED]> wrote:
The problem was if there were indices referencing the column, the indices didn't get dropped and recreated afterwards just like foreign key constrains. For primary key columns, it's the primary key constrain needs to be take care of (drop before alter the column and recreate afterwards).
DdlUtils will drop nothing automatically if you're using the API, you have to remove constraints and index yourself from the model. When using the Ant tasks, the target schema must be a valid schema, so it cannot contain e.g. foreign keys using non-existing columns. Tom
