In Spring Boot you configure the active context with: spring.liquibase.contexts=dev Contexts support logical expressions like context="test or dev" and context="!prod". The ! (not) operator is useful for changeSets you want to run everywhere except production. This gives you a powerful mechanism for maintaining one changeLog that covers all environments without duplicating files or maintaining separate changeLog trees."> In Spring Boot you configure the active context with: spring.liquibase.contexts=dev Contexts support logical expressions like context="test or dev" and context="!prod". The ! (not) operator is useful for changeSets you want to run everywhere except production. This gives you a powerful mechanism for maintaining one changeLog that covers all environments without duplicating files or maintaining separate changeLog trees." />

Prev Next

Database / Liquibase interview questions

What are contexts in Liquibase and how do you use them?

Contexts in Liquibase are labels you attach to a changeSet to control which environments it runs in. When you execute Liquibase and pass a context value (via command line, properties file, or Spring configuration), only the changeSets whose contexts match the active context will be executed. ChangeSets without a context attribute always run regardless of what context is active.

A common use case is seeding test or development data that should never touch production:

<changeSet id="seed-test-users" author="alice" context="test,dev">
    <insert tableName="user">
        <column name="id" value="1"/>
        <column name="email" value="testuser@example.com"/>
    </insert>
</changeSet>

<changeSet id="create-admin" author="alice" context="prod">
    <insert tableName="user">
        <column name="id" value="100"/>
        <column name="email" value="admin@company.com"/>
    </insert>
</changeSet>

In Spring Boot you configure the active context with:

spring.liquibase.contexts=dev

Contexts support logical expressions like context="test or dev" and context="!prod". The ! (not) operator is useful for changeSets you want to run everywhere except production. This gives you a powerful mechanism for maintaining one changeLog that covers all environments without duplicating files or maintaining separate changeLog trees.

What happens to a changeSet that has NO context attribute when Liquibase runs with --contexts=prod?
Which context expression runs a changeSet in all environments except production?

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?
Show more question and Answers...

MuleESB

Comments & Discussions