Uploaded image for project: 'Liquibase Core'
  1. CORE-3418

Wrong table used in column escaping for generating lock SQL

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects versions: 3.6.3
    • Fix versions: None
    • Components: Database Support
    • Environment:

      Not relevant

    • Sprint:

      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.

        Attachments

          Activity

            People

            • Reporter:
              emond.papegaaij Emond Papegaaij
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: