Although Liquibase supports most standard SQL statements with its change tags, there are times when the generated SQL needs to be slightly different for your particular needs. Examples include changing datatypes or adding additional vendor-specific clauses such as “ENGINE INNODB” to CREATE TABLE statements. Since 1.9
Attribute | Description |
---|---|
dbms | The type of a database which that changeSet is to be used for. When the migration step is running, it checks the database type against this
attribute. Valid database type names are listed on the supported databases page. It is possible to list multiple databases separated by commas.
You can also specify that a changeset is NOT applicable to a particular database type by prefixing with ! . The keywords all and none are
also available. |
context | List of contexts in which to run the sql modification. If not specified, is applied in all contexts Since 2.0 |
applyToRollback | Should the sql modification be applied to rollback statements? Default='false' Since 2.0 |
Adds SQL to the beginning of the statement.
Attribute | Description |
---|---|
value | Text to add to beginning of statement |
Adds SQL to the end of the statement.
Attribute | Description |
---|---|
value | Text to add to end of statement |
Replaces all instances of the text specified.
Attribute | Description |
---|---|
replace | Text to replace |
with | Text to replace with |
Replaces all instances of the regular expression specified.
Attribute | Description |
---|---|
replace | Regular expression specifying text to replace |
with | Text to replace with |