Migration bug in H2
Description
Environment
Windows 7 x64
H2 driver version: 1.3.176
Attachments
- 21 Jul 2014, 02:20 PM
Activity
Phạm Hữu Bằng June 15, 2017 at 8:24 AM
3.5.3 also, this problem with case sensitive really blocks the good will of Liquibase.
Petr Hála March 29, 2017 at 8:13 PM
Issue is still present in 3.5.1
Nikolay Seven July 21, 2016 at 12:52 PM
faced the same issue on Liquibase 3.4.2
Nathan Voxland July 23, 2014 at 7:30 PM
The problem is wiht the database_to_upper=false setting. Liquibase only supports the default upper case naming of tables coming back. The fix will have to wait until 3.3
Claudio Seabra July 22, 2014 at 5:13 PM
I'm running only the following command line:
%LIQUIBASE_HOME%/liquibase.bat migrate
All the arguments are in 'liquibase.properties' with following values:
logLevel=DEBUG
changeLogFile=data/esocial.xml
url=jdbc\:h2\:file\:C\:\\dev\\db\\database.db;DATABASE_TO_UPPER\=false;ALIAS_COLUMN_NAME\=true
password=
driver=org.h2.Driver
defaultSchemaName=
username=sa
Only at the first time the migration is running sucessfully.
Details
Details
Reporter
Claudio SeabraComponents
Fix versions
Affects versions
Priority
Major
I am trying to run migrations on my H2 database and the following error is thrown:
Table "DATABASECHANGELOGLOCK" already exists; SQL statement:
PUBLIC.DATABASECHANGELOGLOCK CREATE TABLE (ID INT NOT NULL, LOCKED BOOLEAN NOT NULL, TIMESTAMP LOCKGRANTED, lockedby VARCHAR (255), PK_DATABASECHANGELOGLOCK CONSTRAINT PRIMARY KEY (id)) [42101-179]
The table has already been created previously by liquibase. This tabela should be ignored by it, right?
Is this a bug or am I forgetting anything?