We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When using the CDATA driver with Liquibase v4.23, it results in a TIMESTAMP word appearing in the query when trying to lock the database.
For example
UPDATE [<keyspace_name>].[DATABASECHANGELOGLOCK] SET [LOCKED] = TRUE, [LOCKEDBY] = '<host>', [LOCKGRANTED] = TIMESTAMP '<time>' WHERE [DATABASECHANGELOGLOCK]
Whereas it should appear as
UPDATE [<keyspace_name>].[DATABASECHANGELOGLOCK] SET [LOCKED] = TRUE, [LOCKEDBY] = '<host>', [LOCKGRANTED] = '<time>' WHERE [DATABASECHANGELOGLOCK]
It is specific to when using the CDATA driver.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When using the CDATA driver with Liquibase v4.23, it results in a TIMESTAMP word appearing in the query when trying to lock the database.
For example
UPDATE [<keyspace_name>].[DATABASECHANGELOGLOCK] SET [LOCKED] = TRUE, [LOCKEDBY] = '<host>', [LOCKGRANTED] = TIMESTAMP '<time>' WHERE [DATABASECHANGELOGLOCK]Whereas it should appear as
UPDATE [<keyspace_name>].[DATABASECHANGELOGLOCK] SET [LOCKED] = TRUE, [LOCKEDBY] = '<host>', [LOCKGRANTED] = '<time>' WHERE [DATABASECHANGELOGLOCK]It is specific to when using the CDATA driver.
The text was updated successfully, but these errors were encountered: