status --verbose command

The status --verbose command produces a list of pending changesets with additional information that includes the id, author, and file path name. 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, you need to specify your driver, class path, URL, and user authentication information in your liquibase.properties file. You can also specify these properties in your command line.

Then run the status --verbose command:

liquibase --changeLogFile=postgres_lbpro_master_changelog.xml status --verbose

Note: Enter the name of the changelog you want to use in place of postgres_lbpro_master_changelog.xml.You can also add the changeLogFile to your liquibase.properties file.

status --verbose global attributes

Atrributes Definition Requirement
--changeLogFile The root changelog Required
--username The database username Required
--password The database password Required
--url The JDBC database connection Required

When successful, the status --verbose command produces the following output:

C:\dev\DaticalDB-testing\liquibase-pro-cli-project\postgres_lbpro_master>..\liquibase --changeLogFile=postgres_lbpro_master_changelog.xml status
Liquibase Pro 4.0.0-beta2-LB-337-SNAPSHOT by Datical licensed to Liquibase Pro Customer until Tue Nov 03 19:00:00 CST 2020
Starting Liquibase at 12:55:31 (version 4.0.0-beta2-LB-337-SNAPSHOT #2 built at 2020-06-23 19:48+0000)
21 change sets have not been applied to daticaluser1@jdbc:postgresql://localhost:5433/goku
Liquibase command 'status' was executed successfully.
C:\dev\DaticalDB-testing\liquibase-pro-cli-project\postgres_lbpro_master>..\liquibase --changeLogFile=postgres_lbpro_master_changelog.xml status --verbose
Liquibase Pro 4.0.0-beta2-LB-337-SNAPSHOT by Datical licensed to Liquibase Pro Customer until Tue Nov 03 19:00:00 CST 2020
Starting Liquibase at 12:55:42 (version 4.0.0-beta2-LB-337-SNAPSHOT #2 built at 2020-06-23 19:48+0000)
21 change sets have not been applied to daticaluser1@jdbc:postgresql://localhost:5433/goku
	second_changelog.xml::1::createTableforSynonym-proschema::second
	second_changelog.xml::1::createTable::Liquibase Pro User
	second_changelog.xml::1::createTableforSynonym-proschema::Liquibase Pro User
	postgres_lbpro_master_changelog.xml::4::functionForTrigger::Liquibase Pro User
	postgres_lbpro_master_changelog.xml::1::createView-PROSCHEMA::Liquibase Pro User
	postgres_lbpro_master_changelog.xml::2::dropView-proschema::Liquibase Pro User
	postgres_lbpro_master_changelog.xml::1::createProc-proschema::Liquibase Pro User
	postgres_lbpro_master_changelog.xml::2::dropProc-proschema::Liquibase Pro User
	postgres_lbpro_master_changelog.xml::1::createFunction-proschema::Liquibase Pro User
	postgres_lbpro_master_changelog.xml::2::dropFunc-proschema::Liquibase Pro User
	postgres_lbpro_master_changelog.xml::1::addTrigger-proschema::Liquibase Pro User
	postgres_lbpro_master_changelog.xml::2::disableTrigger-proschema::Liquibase Pro User
	postgres_lbpro_master_changelog.xml::3::enableTrigger-proschema::Liquibase Pro User
	postgres_lbpro_master_changelog.xml::4::renameTrigger-proschema::Liquibase Pro User
	postgres_lbpro_master_changelog.xml::5::dropTrigger-proschema::Liquibase Pro User
	postgres_lbpro_master_changelog.xml::1::addCC-proschema::Liquibase Pro User
	postgres_lbpro_master_changelog.xml::4::dropCC-PROSCHEMA::Liquibase Pro User
	postgres_lbpro_master_changelog.xml::1::dataForTable-proschema::Liquibase Pro User
	postgres_lbpro_master_changelog.xml::2::dataForTable-proschema::Liquibase Pro User
	postgres_lbpro_master_changelog.xml::1::pgExt::liquibase-user
	postgres_lbpro_master_changelog.xml::2::pgExt::liquibase-user
Liquibase command 'status' was executed successfully.