9.12 LIQUIBASE
Database Diff Commands
| New Command | Description |
|---|---|
| diff | Writes description of differences between two databases to standard out. |
| diff-changeLog | Adds any differences between the databases specified to a changelog. Can append in any of the supported changelog formats. |
Database Rollback Commands
| New Command | Description |
|---|---|
| rollback | Rolls back the database to the state it was in when the tag was applied. |
| rollback-sql | A helper command that produces the raw SQL Liquibase would run when using the rollbackByTag command. |
| rollback-to-date | Rolls back the database to the state it was in at the given date/time. |
| rollback-to-date-sql | A helper command that allows you to inspect the SQL Liquibase will run while using the rollback-to-date command. |
| rollback-count | Rolls back the last <value> changesets. |
| rollback-count-sql | Writes SQL to roll back the last <value> changesets to STDOUT. |
| future-rollback-sql | Writes SQL to roll back the database to the current state after the changes in the changelog have been applied. |
| future-rollback-count-sql | Generates the SQL that Liquibase would use to sequentially revert the number of changes associated with undeployed changesets, which are added to a changelog file. |
| future-rollback-from-tag-sql | Produces the raw SQL Liquibase would need to roll back all undeployed changes made up to the specified tag. |
Database Snapshot Commands
| New Command | Description |
|---|---|
| data | Generate changelogs for the data. |
| generate-apex-object | Generate apex objects from a database |
| generate-controlfile | Generate an empty control file that you can use to start a new changelog. |
| generate-db-object | Generate database objects from a database |
| generate-ords-module, generate-ords-schema | Generate ords objects from a database |
| generate-schema | Generate all supported objects in a schema and controller file. |
| generate-changelog | Generate a changelog from a database when adding Liquibase to a new project. This is synonymous with snapshot with the exception of saving the output as XML in the changelog. |
| snapshot | Gathers the current database schema and displays that information to STDOUT. With options, can save the schema in JSON format, and that JSON snapshot can serve as a comparison database. |
| update-to-tag-sql | A helper command that inspects the SQL code Liquibase will run when using the update-to-tag <tag> command. |
Database Update Commands
| New Command | Description |
|---|---|
| update | Updates the database to the current version. |
| update-sql | A helper command that enables you to inspect the SQL code that Liquibase will run when using the update command. |
| update-count | Applies the next <value> changesets. |
| update-count-sql | Writes SQL to apply the next <value> changesets to STDOUT. |
| update-testing-rollback | Updates the database, then rolls back changes before updating again. |
| update-to-tag | Applies sequential changes to your database from the newest changeset to the changeset with the tag you specified and applied earlier. |
| update-to-tag-sql | A helper command that inspects the SQL code Liquibase will run when using the update-to-tag <tag> command. |
Documentation Commands
| New Command | Description |
|---|---|
| db-doc | Generates Javadoc-like documentation based on current database and changelog. |
Maintenance Commands
| New Command | Description |
|---|---|
| calculate-checksum | Calculates and prints a checksum for the changeset with the specified id in the following format: filepath::id::author. |
| changelog-sync | Marks all changes as executed in the database. |
| changelog-sync-sql | Writes SQL to mark all changes as executed in the database to STDOUT. |
| changelog-sync-to-tag | Marks all undeployed changesets from your changelog up to and including the specified tag as executed in your database. |
| changelog-sync-to-tag-sql | Produces the raw SQL that Liquibase would run when using the changelog-sync-to-tag command to mark all undeployed changesets associated with the specified tag as executed in your database. |
| clear-checksums | Removes current checksums from database. On next update changesets that have already been deployed will have their checksums recomputed, and changesets that have not been deployed will be deployed. |
| drop-all | Drops all database objects owned by the user. |
| list-locks | Lists who currently has locks on the database changelog. |
| mark-next-changeset-ran | Mark the next changeset as executed in the database. |
| mark-next-changeset-ran-sql | Inspects the SQL Liquibase will run while using the mark-next-changeset-ran command. |
| release-locks | Releases all locks on the database changelog. |
| tag | "Tags" the current database state for future rollback. |
| tag-exists | Checks whether the given tag already exists. |
| unexpected-changesets | Produces a list of changesets that were run in the database but do not exist in the current changelog. |
| validate | Checks the changelog for errors. |