Discussion:
[Liquibase-user] New Topic: Column "locked" is not found by case-sensitive databases (patch is attached)
Liquibase Community Forum
2010-10-13 13:20:22 UTC
Permalink
A new topic, 'Column "locked" is not found by case-sensitive databases (patch is attached)', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=741.new#new

The text of the topic is shown below:

Hi Nathan,

since Liquibase 2.0 RC6 we get the following error when updating our databases:
Error executing SQL SELECT "locked" FROM "DATABASECHANGELOGLOCK" WHERE "ID"=1

Background:
We use our databases in a case-sensitive way to improve readability of table names, constraint names, and so on.

The correct SQL statement must therefore look like:
SELECT "LOCKED" FROM "DATABASECHANGELOGLOCK" WHERE "ID"=1

The appended patch.txt solves this problem.
We have tested this patch successfully with all of our databases: DB2, H2, MSSQL, Oracle, PostgreSQL.

Perhaps this is also a solution of the following bug report: http://liquibase.jira.com/browse/CORE-506
(concerns the comment by Oliver Libutzki on 05/Oct/10 7:36 AM.)

Kind regards,
Markus Müller

Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=1.0

Regards,
The Liquibase Community Forum Team.

Loading...