status
The status
command states the number of undeployed changesets. The status
command does not modify the database.
Note: Most often the command attribute --verbose
is used alongside the status
command like so:
status --verbose
The status --verbose
command lists all undeployed changesets. It also lists the id, author, and file path name for each undeployed changeset. The status --verbose
command does not modify the database.
Uses
The status --verbose
command is typically used when changesets were added to a changelog through source control by another developer. The command confirms what has been deployed and what changesets are pending per author and corresponding IDs.
Running the status --verbose
command
To run the status --verbose
command, specify the driver, classpath, and URL in the properties file. You can also specify these properties in your command line.
Run the status --verbose
command:
liquibase --changelog-file=<postgres_lbpro_master_changelog.xml> status --verbose
where <postgres_lbpro_master_changelog.xml>
represents the name of the changelog.
Note: Add the changelog-file
to the Liquibase properties file to save time and reduce errors.
status --verbose
global attributes
Atrributes | Definition | Requirement |
---|---|---|
--changelog-file
|
The root changelog | Required |
--username
|
The database username | Required |
--password
|
The database password | Required |
--url
|
The JDBC database connection | Required |
Note: The username
and password
attributes are not required for connections and systems which use alternate means of authentication.

When successful, the status --verbose
command produces the following output:
Liquibase Version: 4.9.1
Liquibase Community 4.9.1 by Liquibase
3 change sets have not been applied to DBUSER@jdbc:h2:tcp://localhost:9090/mem:dev
example-changelog.sql::1::your.name
example-changelog.sql::2::your.name
example-changelog.sql::3::other.dev
Liquibase command 'status' was executed successfully.