We're updating the issue view to help you get more done. 

Wrong table used in column escaping for generating lock SQL

Description

LockDatabaseChangeLogGenerator incorrectly uses database.getDatabaseChangeLogTableName() in the call to escapeColumnName for the ID column. Notice the missing Lock. This probably does not affect the generated SQL, but it is not consistent and might cause unforeseen issues with custom implementations.

Environment

Not relevant

Status

Assignee

Unassigned

Reporter

Emond Papegaaij

Labels

None

Components

Affects versions

3.6.3

Priority

Minor