Skip to:

Skip to Jira Navigation
Skip to Side Navigation
Skip to Main Content

Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)

Liquibase Core - No new issues - report new issues in GitHub

Software project

Menu

You're in a company-managed project

Liquibase Core - No ...

mysql case insensitive affects databasechangelog creation

Description

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.

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

Reporter

Horia Constantin

Horia Constantin

Components

Fix versions

Affects versions

Priority

Minor

Created November 18, 2013 at 10:57 AM

Updated December 10, 2013 at 9:14 PM

Resolved December 10, 2013 at 9:14 PM