For large projects it is common to split the changeLog into multiple files organised by version or feature, and then include them from a root changeLog using the or tags. This keeps individual files manageable and makes code reviews easier — each pull request only adds a new changeSet file rather than modifying a single growing file."> For large projects it is common to split the changeLog into multiple files organised by version or feature, and then include them from a root changeLog using the or tags. This keeps individual files manageable and makes code reviews easier — each pull request only adds a new changeSet file rather than modifying a single growing file." />

Prev Next

Database / Liquibase interview questions

What is a changeLog in Liquibase?

A changeLog is the master configuration file (or set of files) that contains all the database changes Liquibase should manage. It acts as the single source of truth for every schema modification your application has ever needed — from the initial table creation to the latest column rename. Liquibase reads this file on every run and decides which changeSets to apply based on what's already recorded in the database tracking table.

A changeLog can be written in four formats: XML, YAML, JSON, or formatted SQL. XML is the most common in enterprise Java projects. Here's a minimal example:

<?xml version="1.0" encoding="UTF-8"?>
<databaseChangeLog
    xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog
        http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-4.9.xsd">

    <changeSet id="1" author="alice">
        <createTable tableName="customer">
            <column name="id" type="BIGINT" autoIncrement="true">
                <constraints primaryKey="true" nullable="false"/>
            </column>
            <column name="email" type="VARCHAR(255)"/>
        </createTable>
    </changeSet>
</databaseChangeLog>

For large projects it is common to split the changeLog into multiple files organised by version or feature, and then include them from a root changeLog using the <include> or <includeAll> tags. This keeps individual files manageable and makes code reviews easier — each pull request only adds a new changeSet file rather than modifying a single growing file.

Which Liquibase changeLog format is most common in enterprise Java projects?
How do you split a large Liquibase changeLog across multiple files?

Invest now in Acorns!!! 🚀 Join Acorns and get your $5 bonus!

Invest now in Acorns!!! 🚀
Join Acorns and get your $5 bonus!

Earn passively and while sleeping

Acorns is a micro-investing app that automatically invests your "spare change" from daily purchases into diversified, expert-built portfolios of ETFs. It is designed for beginners, allowing you to start investing with as little as $5. The service automates saving and investing. Disclosure: I may receive a referral bonus.

Invest now!!! Get Free equity stock (US, UK only)!

Use Robinhood app to invest in stocks. It is safe and secure. Use the Referral link to claim your free stock when you sign up!.

The Robinhood app makes it easy to trade stocks, crypto and more.


Webull! Receive free stock by signing up using the link: Webull signup.

More Related questions...

What is Liquibase and what problem does it solve? What is a changeLog in Liquibase? What is a changeSet in Liquibase and how is it identified? What are the DATABASECHANGELOG and DATABASECHANGELOGLOCK tables? What is the difference between Liquibase and Flyway? What are contexts in Liquibase and how do you use them? What are labels in Liquibase and how do they differ from contexts? How does rollback work in Liquibase? What is a Liquibase precondition and why would you use one? How do you integrate Liquibase with Spring Boot? What are Liquibase change types and can you name common ones? What is the Liquibase diff command and when is it useful? What are Liquibase tags and how do you use rollback to a tag? What is runOnChange and runAlways in a Liquibase changeSet? What is the markNextChangeSetRan and markNextChangeSetRanSQL command used for? How do you manage Liquibase changeLog files in a multi-module Maven project? What is the Liquibase updateSQL command and when is it used? What is a Liquibase snapshot and what commands use it? What is the failOnError attribute in a changeSet and when should you set it to false? How does Liquibase handle transactions during migration? What is the Liquibase Hub and what does it provide? How do you use Liquibase with multiple databases or schemas in a single application? What is the Liquibase Pro checksum validity and how do clearCheckSums and validChecksums work? What are Liquibase custom change types and how do you create one? How do you handle large table migrations in Liquibase without causing downtime? What is the Liquibase Maven plugin and how do you run migrations with it? What is the Liquibase status command and how does it differ from validate? What are Liquibase property substitution and how does it work? How do you write Liquibase changeLogs in YAML format? What is the Liquibase formatted SQL changeLog format? What is the Liquibase updateTestingRollback command? How do you use Liquibase with Docker and Testcontainers in integration tests? What is the difference between addColumn with a default value and a nullable column in Liquibase for large tables? What is liquibase.properties and what configuration belongs in it?


Comments & Discussions