fails with mssql 2005 because of using true/false (instead of 0/1 in older versions) while working with bit fields

Description

running any update causing next error:

Starting Liquibase ... (version 3.6.1 built at 2018-04-11 08:41:04)
Unexpected error running Liquibase: Error executing SQL UPDATE dbo.DATABASECHANGELOGLOCK SET LOCKED = TRUE, LOCKEDBY = '...', LOCKGRANTED = '...' WHERE ID = 1 AND LOCKED = FALSE: Invalid column name 'FALSE'.

it's because of mssql accepts 0/1/null as values for bit fields.

Environment

ws2008r2, mssql

Status

Assignee

Unassigned

Reporter

Eduard Panov

Labels

None

Affects versions

Priority

Blocker
Configure