You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use manual as a column name.
When updating from MySQL 8.0 to 8.4, this is now a reserved keyword but Liquibase does not recognize it as such and doesn't quote it in table creation statements when using the default objectQuotingStrategy, leading to an error.
Steps To Reproduce
Use the manual keyword as column name in a Liquibase changeset for createTable, using the default objectQuotingStrategy.
Expected/Desired Behavior
Liquibase should quote reserved keywords even when objectQuotingStrategy=LEGACY
Liquibase Version
4.28.0
Database Vendor & Version
MySQL 8.4
Liquibase Integration
No response
Liquibase Extensions
No response
OS and/or Infrastructure Type/Provider
No response
Additional Context
No response
Are you willing to submit a PR?
I'm willing to submit a PR (Thank you!)
The text was updated successfully, but these errors were encountered:
Search first
Description
We use
manual
as a column name.When updating from MySQL 8.0 to 8.4, this is now a reserved keyword but Liquibase does not recognize it as such and doesn't quote it in table creation statements when using the default
objectQuotingStrategy
, leading to an error.Steps To Reproduce
Use the
manual
keyword as column name in a Liquibase changeset forcreateTable
, using the defaultobjectQuotingStrategy
.Expected/Desired Behavior
Liquibase should quote reserved keywords even when
objectQuotingStrategy=LEGACY
Liquibase Version
4.28.0
Database Vendor & Version
MySQL 8.4
Liquibase Integration
No response
Liquibase Extensions
No response
OS and/or Infrastructure Type/Provider
No response
Additional Context
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: