mysql case insensitive affects databasechangelog creation
Description
Environment
windows 8.1 x64, 5.6.14 MySQL Community Server
Activity
Show:
Nathan Voxland December 10, 2013 at 9:14 PM
Working for me currently. I think it was fixed by a seprate bug
Fixed
Details
Details
Reporter
Horia Constantin
Horia ConstantinComponents
Fix versions
Affects versions
Priority
MinorCreated November 18, 2013 at 10:57 AM
Updated December 10, 2013 at 9:14 PM
Resolved December 10, 2013 at 9:14 PM
databaseChangeLogLockTable and databaseChangeLogTable are always used as uppercase by Liquibase. The first time running liquibase all is ok.
The problem appears when trying to use it again (it fails because it tries to create the tables again). Apparently, it fails to detect the already existing tables (mysql is case insensitive).
the currently workaround: I am passing java system properties:
-Dliquibase.databaseChangeLogLockTableName=databasechangeloglock
-Dliquibase.databaseChangeLogTableName=databasechangelog
Maybe another issue is that I can't change the bean configuration to send them from there.