Skip to content

Liquibase changelog

Team Edition lets you generate a Liquibase Changelog from any schema, database, or container. It captures your current structure as creation statements, so you can recreate it later, store it in version control, or plug it into migration workflows. Under the hood, Team Edition uses Liquibase snapshots to read your metadata and convert it into a changelog format. A changelog contains only structural metadata - tables, views, keys, sequences, and other supported objects. It doesn’t include table data.

Info

Changelog generation works with most major databases and structural objects supported by your database.

Liquibase Changelog process

Select containers or objects

  1. In the Database Navigator, select one or more containers you want to use
  2. Open the context menu

  3. Choose Compare/Migrate -> Liquibase Changelog

Specify objects for changelog

  1. Make sure you selected the correct containers or objects

  2. If everything looks right, click Next

Changelog settings

  1. Review and adjust the settings you want to use

    Setting Description
    Export result to the file Saves the generated diff to a file instead of showing it in the viewer.
    Output folder Folder where the generated file will be saved. Enabled only when Export result to the file is turned on.
    Output file pattern Lets you use variables such as database name or timestamp to build the file name. Enabled only when Export result to the file is turned on. See more details about Pre-configured variables.
    Report Engine Selects the output format: DDL, Change Log, JSON, YAML, or Plain text. Enabled only when Export result to the file is turned on.
    Object types Chooses which structural objects to include in comparison (tables, columns, keys, views, etc.). With Liquibase PRO, you can work with extended metadata. For details, see the Liquibase PRO guide.

    Info

    Liquibase Changelog generation uses the same global settings as Schema Compare. To adjust quoting, case handling, or logging, use the Schema Compare preferences.

  2. Click Proceed to generate the changelog

Tip

You can export the results of a Schema Compare operation to a remote file system via Cloud Storage using the Browser remote file system button .

Results view

By default, you get a DDL view of the generated changelog. It shows the structural statements produced from your containers or objects and lets you review the result before saving or exporting it.

Use the action panel to manage the results:

Button/Option Description
All Enables all changes in the changes tree.
None Disables all changes in the changes tree.
Refresh Report Updates the comparison report to reflect any changes made to the selection or schema.
Show log Opens the Schema Compare log. You can control the log detail level in Preferences.
Export Exports the current changelog report to a .txt file.
Save Saves the current state of the report.
Copy Copies the generated SQL or report text to the clipboard.
Open in Editor Opens the current changelog report in the SQL Editor.

Save operation as a task

If you generate changelogs regularly, save the operation as a task. You can run it anytime or add it to a schedule.

You can also include Changelog generation in a composite task. For example, if you export the result as a script, the next step in the composite task can run that script automatically.