DBDeploy breaks if table called change_log already exists with different structure

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a custom changelog table in your DB.
2. Execute the changelog script from DBDeploy against your DB
3.

What is the expected output? What do you see instead?
Failure is expected here

What version of the product are you using? On what operating system?
3.0MQ

Please provide any additional information below.

Problem is that DBDeploy (that I can find) doesn't support a way for separating 
the permissions used on the changelog table from others. 

I can't put DBDeploys change log table in my main schema because I already have 
a changelog table (which is such a generic name that changing the table to 
something dbdeploy specific would be better). And I am not given a config 
option to move the changelog table to a separate schema so I can work around 
this. My concern is that I am going to have to change the source code to allow 
me to change the changelog table name to get dbdeploy to work. 

So I need to be able to specify a schema for the changelog table to be in that 
is potentially separate from the default schema for the user that DBDeploy is 
acting as. THis is becuase the dbdeploy user really needs to have write 
permissions to my main schema to affect the changes. 

Original issue reported on code.google.com by JESmit...@gmail.com on 12 Jul 2011 at 3:00

[GoogleCodeExporter]

You can already specify your own changelog table name. --changeLogTableName 
my-change-log from the command line or <dbdeploy 
changeLogTableName="my-change-log" /> from ant

Original comment by longs...@gmail.com on 25 Jul 2011 at 2:15