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

Reporter

Emond Papegaaij

Components

Affects versions

Priority

Minor
Configure