CODEWITHSUNDEEP
oracle-databasepostgresql-9.1liquibase
devang
devang

Reputation: 5516

Liquibase: Custom SQL statement

I have my liquibase schema defined initially for PostreSQL. Now, I have to modify the schema file to support Oracle. I have a change-set that has a <sql> tag. It has a query that accesses the pg_catalog table to set a value to the sequence. However, this will not work for Oracle. If I remove it, the Liquibase complains with check-sum validation fail. It complains even if I have an empty <sql> tag or some other query specified within. Within this change-set, I have many other create-table statement, so I cannot just remove oracle from dbms attribute. Is there any way I can suppress this sql from running for Oracle?

Upvotes: 0

Views: 3142

Answers (1)

Mark O&#39;Connor
Mark O&#39;Connor

Reputation: 77951

The dbms attribute on the changeset is the mechanism designed to handle this problem..... Sounds like you're trying to do too much within one changesest (but I guess you've figured that out)

The checksum validation failure is liquibase's safety mechanism designed to defend the database against someone tampering with the schema files.

How to fix it is to use the clearChecksums option when running liquibase. It tells liquibase to recompute the checksums for the changesets already in the database. This will enable your postgres database instance to accept the alterations to its changesets that you've made for Oracle.

Upvotes: 1

Related Questions