generateChangeLog command creates a changelog file that has a sequence of changesets which describe how to re-create the current state of the database.
generateChangeLog command is typically used when you want to capture the current state of a database, then apply those changes to any number of databases. This is typically only done when a project has an existing database, but hasn't used Liquibase before. See How to set up Liquibase with an Existing Project and Multiple Environments for more details.
Note: When using the update command to apply the changes in the changelog, Liquibase will not create a new database or schema. You must create them before applying the changelog to it.
To generate a changelog:
- Configure the liquibase.properties file to include your driver class path, URL, and user authentication information for the database you want to capture.
Note: For information on how to configure your
liquibase.properties file, view the Creating and configuring a liquibase.properties file topic. Instead of using a
liquibase.properties file, you can also pass the necessary information on the command line.
- Open your command prompt or Linux terminal and run the following command:
generateChangeLog Global Parameters
|–changeLogFile||Specifies the root changelog.||Required|
|–url||Specifies the JDBC database connection URL.||Required|
|–username||Specifies the database username.||Required|
|–password||Specifies the database password.||Required|
|–liquibaseProLicenseKey||Your Liquibase Pro license key.||Optional|
generateChangeLog command parameters
|–defaultCatalogName=<name>||Default database catalog to use.||Optional|
|–defaultSchemaName=<name>||Default database schema to use.||Optional|
|–schemas=<name1, name2>||Database schemas you want to include.||Optional|
|–outputSchemaAs=<name1,name2>||Can be used to||Optional|
|–includeCatalog=[boolean]||If true, the catalog will be included in generated changesets. Defaults to false.||Optional|
|–includeSchema=[boolean]||If true, the schema will be included in generated changesets. Defaults to false.||Optional|
|–includeTablespace=[boolean]||If true, the tablespace of tables and indexes will be included. Defaults to false.||Optional *|
|–dataOutputDirectory=DIR||Output data as CSV in the given directory||Optional|
|–diffTypes||List of diff types to include in changelog expressed as a comma separated list (no spaces) from: catalog,tables,functions,views,columns,indexes,foreignkeys,primarykeys,uniqueconstraints,data,storedprocedure,triggers,sequences.||Optional **|
* The default value of
--includeTablespaceonly captures the tablespace if it was specified in the create table statement.
** If this is null then the default types will be: tables, views, columns, indexes, foreignkeys, primarykeys, uniqueconstraints.
generateChangeLog command generates a changelog that contains all of your Objects (represented as changesets) and places the file in the same directory where the command was ran.
The extension provided determines the format of the changelog, so if you specify the filename as
changelog.xml you will get an XML formatted changelog. However, if you specify the filename as
changelog.postgresql.sql you will get changelogs formatted in YAML or JSON or SQL, respectively.
Note: When generating an SQL formatted changelog, you must specify the short name of the targeted database type as part of the filename (as shown above). Liquibase Community
Liquibase Community changelog
Additional functionality with Liquibase Pro
While Liquibase Community stores all changesets in a changelog, Liquibase Pro creates a directory called Objects and places the directory at the same level as your changelog. The Objects directory contains a subdirectory for each of the following stored logic types.
- stored procedure
Note: Not all database platforms support all of these types.