Using Liquibase with Firebird

Firebird is an open-source relational database management system. For more information, see Firebird RDBMS Documentation.

Supported Versions

  • 3.0
  • 4.0

Note: The supported versions are the versions that were tested with Liquibase Test Harness.


Before using Liquibase with your database, ensure you have:

Install Drivers

To use Liquibase and Firebird, you need to have the JDBC driver JAR file.

Liquibase comes with a pre-installed driver for this database in the liquibase/lib directory. For more information, see Adding and Updating Liquibase Drivers.

Note: If you placed the JAR file in a different directory, you must specify the path in the Liquibase properties file: classpath:../<path_to_drivers>/<db_jar_name>.jar. For more information, see Specifying Properties in a Connection Profile.

If you use Maven, you also need to download the driver JAR file and put the driver in a location that your Maven build can access. Configure the Maven pom.xml file to use the local copy of the driver JAR file. For example:


Test Your Connection

For Liquibase and Firebird to work, you need to:

  1. Ensure your Firebird database is configured. See the Firebird Quickstart Guide for more information.
  2. Specify the database URL in the Liquibase properties file:
  3. url: jdbc:firebirdsql://localhost:3050//firebird/data/testdb
  4. Create a text file called changelog (.xml, .sql, .json, or .yaml) in your project directory and add a changeset.
  1. Navigate to your project folder in the CLI and run the Liquibase status command to see whether the connection is successful. You can pass arguments in the CLI or keep them in the Liquibase properties file.
  2. liquibase --username=test --password=test --changelog-file=<changelog.xml> status
  3. Run your first update with the update command, which makes changes to your database. You can also run the update-sql command to inspect the SQL before running the update command.
  4. liquibase --changelog-file=<changelog.xml> update-sql
    liquibase --changelog-file=<changelog.xml> update

From a database UI tool, ensure that your database contains the table you added along with the DATABASECHANGELOG table and DATABASECHANGELOGLOCK table.

If you run the update command to deploy your changesets and receive the error message related to the DATABASECHANGELOGLOCK table issue, manually create the DATABASECHANGELOGLOCK table using SMALLINT type instead of BOOLEAN:


See also