Migrations not running in database migration 1.1

[sethfuller]

I just upgraded to database migration 1.1 today from 1.0 and tried to run some database migrations that were not run for my production database. The DATABASECHANGELOG table is not updated with the changes and they are not run. Is there some incompatible change between 1.1 and 1.0. I used the dbm-update command to run changes created with dbm-gorm-diff under database migration 1.0. My Grails version is 2.0.4.

[ideasculptor]

On Mon, Jun 25, 2012 at 3:02 PM, sethfuller <[hidden email]> wrote:

I just upgraded to database migration 1.1 today from 1.0 and tried to run
some database migrations that were not run for my production database. The
DATABASECHANGELOG table is not updated with the changes and they are not
run. Is there some incompatible change between 1.1 and 1.0. I used the
dbm-update command to run changes created with dbm-gorm-diff under database
migration 1.0. My Grails version is 2.0.4.

I don't have any specific information, as I have 1.1 working without issue in 2.0.3, but I did discover that the plugin provides no feedback about problems unless you specify --verbose when you run dbm-upgrade.  It just silently fails with no output.  If you use --verbose, you'll likely get an error message and stacktrace that will help you figure out your problem

[sethfuller]

Thanks for the tip. It looks like the connection is timing out and it is happening now with both database migration 1.0 and 1.1, it just started happening after I upgraded so it is unrelated.