Liquibase serves as a critical tool for robust database version control and automated schema change management, primarily used by organizations to ensure consistency and deployment efficiency. In TrustRadius reviews, its foundational role in tracking database evolution and facilitating controlled DDL/DML operations is frequently highlighted. It integrates seamlessly into CI/CD pipelines, enabling automated and repeatable deployments, which significantly contributes to automation and overall efficiency.

While reviewers note significant improvements in deployment speed and reduced errors, with some reporting up to a 70% reduction in deployment time, areas for improvement include the complexity of rollbacks for intricate changes and challenging error handling, which can halt pipelines. Overall, users find Liquibase enhances database administration by reducing manual errors and streamlining deployments, though it requires initial investment in technical expertise.

Pros

Comprehensive Change Tracking and Versioning
Reliable Rollback Capabilities
Seamless CI/CD Integration and Automation
Improved Deployment Speed and Efficiency
Significant Reduction in Schema-Related Errors

Cons

Complexity of Rollbacks for Intricate Changes
Challenging Error Handling and Reporting
Cumbersome Changelog Organization for Large Projects
Less Efficient IDE and Git Integration
Requires Significant Initial Technical Expertise

From 13 reviews | Last Published May 27, 2026

Why it matters:

Reviewers highly value Liquibase's ability to meticulously track and version every database schema change, with 10 of 13 reviewers highlighting this as a core strength. This functionality, often managed through changelog files, provides an auditable history of modifications, which is crucial for compliance and administrative oversight. The system's record-keeping ensures schema consistency and allows for easy review of deployment history.

“Liquibase allows us to track every change made to the database schema using changelog files (XML, YAML, or SQL) where this change is tracked, auditable, and can be rolled back if needed from DATABASECHANGELOG table which eventually helps in being compliant and trackable which are mandatory in my company as we are part of a healthcare organization.”

Why it matters:

Reviewers frequently commend Liquibase for significantly accelerating deployment cycles and enhancing overall efficiency. The tool's automation and version control capabilities are cited as key drivers, enabling faster changes across environments and reducing deployment times. This contributes to greater agility and autonomy for development and operations teams.

“By using Liquibase it allows faster deployment cycle across environment where changes are automated and version-controlled, reducing deployment time by up to approx 70%.”

Why it matters:

The primary use case for Liquibase, as identified by 7 of 13 reviewers, is its capability for comprehensive database version control. This functionality allows organizations to track and manage all database changes, from schema modifications to data updates, in a structured and auditable manner. Reviewers leverage it to maintain a centralized schema-management system, ensuring consistency and traceability across different database types and environments.

“We are currently using Liquibase in our project for handling any database management and version control activity changes on MySQL database server.”

Liquibase is designed to make database administration, especially changes and deployments, safer and easier. How did using Liquibase affect your organization’s database administration experience?

From 13 reviews | Last Published May 27, 2026

Summary

Liquibase significantly enhances database administration by reducing manual errors and streamlining deployments, according to user feedback. Nearly half of the reviewers (46%) noted a decrease in errors, attributing this to Liquibase's consistent, version-controlled process for managing schema changes. This structured approach helps prevent inconsistencies that often arise from manual or ad hoc script applications. Concurrently, 46% of reviewers highlighted how the tool streamlines database deployments, particularly through seamless integration with CI/CD pipelines. This integration reduces manual interventions, accelerates release cycles, and allows DBAs to focus on strategic tasks rather than repetitive operations. Additionally, 23% of reviewers indicated that Liquibase improves the ability to track and audit database changes, making it easier to monitor work and revert issues. These combined benefits contribute to a more reliable and efficient database administration experience, fostering greater confidence and reducing the risk of downtime.

Top Quotes

Reduced Manual Errors

“DBAs no longer need to manually track or apply SQL scripts across environments which impacted in reducing manual errors as Liquibase provides consistent, version-controlled process for managing schema changes.”

Streamlined Deployments

“reduced bottlenecks in release cycles and with integration to CI/CD pipeline for database deployments DBAs spend less time on repetitive tasks and more time on strategic initiatives with reduce risk of any downtime or DB outage.”

Improved Tracking and Auditing

“Liquibase has made it easier to track changes and to revert bad changes.”

What positive or negative impact (i.e. Return on Investment or ROI) has Liquibase had on your overall business objectives?

From 13 reviews | Last Published May 27, 2026

Summary

Reviewers largely indicate that Liquibase positively impacts business objectives by enhancing deployment processes and reducing operational errors. A significant majority of reviewers, 8 of 13, highlighted improvements in deployment speed and efficiency, with some reporting up to a 70% reduction in deployment time due to automation and version control capabilities. This increased agility allows for more frequent and reliable deployments across various environments. Furthermore, 6 of 13 reviewers noted a substantial decrease in errors and production incidents, with specific mentions of 30-40% downtime reduction and 60-70% fewer schema-related issues. These improvements contribute to greater stability and reduced operational costs. However, 3 of 13 reviewers also pointed to challenges related to the complexity and expertise required for integration and ongoing management, suggesting that initial investment in technical knowledge and setup time can be considerable, potentially creating single points of failure if expertise is not widely distributed. The tool also contributes to improved auditability and traceability, noted by 3 reviewers, and supports scalability and future growth, mentioned by 2 reviewers, by establishing standardized schema change practices.

Top Quotes

Deployment Speed and Efficiency

“By using Liquibase it allows faster deployment cycle across environment where changes are automated and version-controlled, reducing deployment time by up to approx 70%.”

Error and Incident Reduction

“Liquibase usage has drastically reduced database downtime with rollback capabilities and pre-deployment validation and helps in preventing bad schema changes from causing outages where in my current project estimated downtime reduction of 30–40%.”

Complexity and Expertise Required

“Trying to get Liquibase integrated into a pipeline has taken time investment and required some trial and error.”

Besides Liquibase, what other software do you regularly use? How likely would you be to recommend it to a friend or colleague?

From 13 reviews | Last Published May 27, 2026

Summary

Reviewers frequently integrate other software into their development workflows alongside Liquibase, primarily for database interaction, management, and continuous integration/delivery processes. A significant portion of the reviewed feedback, from 5 of 13 reviewers, highlighted the regular use of various Database IDEs for day-to-day database development and querying. Complementing these IDEs, 4 of 13 reviewers also indicated reliance on specialized Database Tools, suggesting a need for more focused database administration or development functionalities. Furthermore, a smaller but notable segment of the feedback, from 2 of 13 reviewers, pointed to the use of CI/CD and DevOps platforms, indicating an emphasis on automating and streamlining database change management within broader software delivery pipelines. The variety of tools mentioned across these categories suggests that users are building comprehensive ecosystems around Liquibase to support diverse aspects of their database operations.

Top Quotes

Database IDEs

“DbVisualizer, MySQL Workbench”

Database Tools

“Redgate Flyway”

CI/CD and DevOps

“Jenkins, Harbor, Azure DevOps Server”

Describe how you use Liquibase in your organization. What are the business problems the product addresses and what is the scope of your use case?

From 13 reviews | Last Published May 27, 2026

Summary

Liquibase is primarily utilized by organizations for robust database version control and automated schema change management, addressing critical business problems related to consistency and deployment efficiency. A majority of reviewers, 7 out of 13, specifically highlight its role in database version control, indicating its foundational importance for tracking and managing database evolution. This capability extends to schema change management, cited by 6 of 13 reviewers, where Liquibase facilitates the controlled deployment of DDL and DML operations across various database environments. Furthermore, 5 of 13 reviewers emphasize its seamless integration into CI/CD pipelines, enabling automated and repeatable deployments. This integration, coupled with its core versioning features, significantly contributes to automation and efficiency, a benefit noted by 5 of 13 reviewers, who report reduced deployment times and minimized manual errors.

Top Quotes

CI/CD Integration

“As part of our DevOps automation strategy it is integrated into our CI/CD pipelines using github actions pipeline deployments to manage schema changes across multiple environments from Dev to Stage and then to Prod in a controlled and repeatable way.”

Database Version Control

“We are currently using Liquibase in our project for handling any database management and version control activity changes on MySQL database server.”

Schema Change Management

“This involves creating any database user or any other DDL and DML database transactions involving table, index creations along with modifying or altering existing tables/views/indexes.”

Please provide some detailed examples of areas where Liquibase has room for improvement.

From 13 reviews | Last Published May 27, 2026

Summary

Reviewers of Liquibase frequently identify several areas where the product could be enhanced to improve user experience and workflow efficiency. A primary concern, raised by 4 of 13 reviewers, is the complexity associated with rollbacks, particularly for intricate changes, which often necessitate manual intervention and are difficult to manage. Closely related to this is the product's error handling and reporting, which 3 of 13 reviewers found challenging, citing difficulties in interpreting error messages and the system's tendency to halt pipelines on single connection failures. Beyond issue resolution, users also highlighted challenges in daily development workflows. Two reviewers noted that changelog organization can become cumbersome, especially with large files or when managing specific database object types like MySQL stored procedures. Additionally, 2 of 13 reviewers expressed a desire for better integration with popular Integrated Development Environments (IDEs) and more intuitive Git integration, suggesting that current tooling can make changeset management less efficient.

Top Quotes

Rollback complexity

“While Liquibase supports rollbacks, they often require manual intervention fgor complex changes for example in data migrations or multi-step schema changes, rollback logic can be hard to write and maintain.”

Error handling and reporting

“I would like Liquibase to explore all errors in the changelog files compared to one at a time. We spent a lot of time troubleshooting one error at a time versus having a batch log of errors in each file.”

Changelog organization and size

“If two developers create changes with the same id in different files, Liquibase will throw a conflict even if they’re for different modules, along with this changelog files can become large and difficult to organize.”

Please provide some detailed examples of things that Liquibase does particularly well.

From 13 reviews | Last Published May 27, 2026

Summary

Liquibase is consistently recognized by reviewers for its robust capabilities in managing database schema changes. A primary strength, highlighted by 10 of 13 reviewers, is its comprehensive Change Tracking and Versioning system, which provides auditable records and ensures consistency across schemas. This foundational feature underpins other key benefits, such as the ability to Rollback Capabilities, cited by 6 of 13 reviewers, offering a critical safety net for database operations. Furthermore, 5 of 13 reviewers commend Liquibase for its seamless CI/CD Integration and Automation, facilitating automated deployments across various environments and reducing manual intervention. The platform's ability to automate and track changes is frequently linked to improved compliance and easier administration for database professionals. While less frequently mentioned, 2 of 13 reviewers also appreciate its Database Schema Comparison functionality, which aids in synchronizing schemas and verifying deployments.

Top Quotes

Change Tracking and Versioning

CI/CD Integration and Automation

“It helps in supporting deploying the same changelog across multiple environments (dev, staging, prod) without any manual intervention from CI/CD github actions pipeline.”

Rollback Capabilities

“where this change is tracked, auditable, and can be rolled back if needed from DATABASECHANGELOG table which eventually helps in being compliant and trackable which are mandatory in my company as we are part of a healthcare organization.”

View All Reviews

Liquibase Reviews

72 Reviews

Liquibase a Great Database Management Tool.

Rating: 10 out of 10

Incentivized

September 17, 2025

Use Cases and Deployment Scope

In developing our application, we use Liquibase to maintain and build our database structures. We use it to apply changes and additions to our database and keep track of the changes being made. Liquibase has allowed us to better maintain control over the evolution of our data structures.

Pros

Keeps a change log of all change made.
Has the ability to rollback when needed.
Easily document changes.

Cons

Make it easier to roll back changes.
Add a GUI to examine the change logs.
Continue the good work.

Likelihood to Recommend

It enables the team to track all changes made to the database. These changes can be stored in a repository and easily tracked within the Liquibase ecosystem.

Ashton Judson

Principal Automation Engineer in Engineering at FinQuery (201-500 employees)

Vetted Review

5 years of experience

Liquibase Review

Rating: 10 out of 10

Incentivized

September 10, 2025

Use Cases and Deployment Scope

We are currently using Liquibase in our project for handling any database management and version control activity changes on MySQL database server. This involves creating any database user or any other DDL and DML database transactions involving table, index creations along with modifying or altering existing tables/views/indexes. As part of our DevOps automation strategy it is integrated into our CI/CD pipelines using github actions pipeline deployments to manage schema changes across multiple environments from Dev to Stage and then to Prod in a controlled and repeatable way. Liquibase is helping in solving our few business problems that includes reducing any database changes deployment time, human prone errors and manual efforts to add database changes on various environments and helps in tracking all database changes as part of a well defined version control system and Liquibase tracks all the database changes in DATABASELOGCHANGE table it helps in tracking and auditing purposes.

Pros

Liquibase allows us to track every change made to the database schema using changelog files (XML, YAML, or SQL) where this change is tracked, auditable, and can be rolled back if needed from DATABASECHANGELOG table which eventually helps in being compliant and trackable which are mandatory in my company as we are part of a healthcare organization.
It helps in supporting deploying the same changelog across multiple environments (dev, staging, prod) without any manual intervention from CI/CD github actions pipeline.
It helps in comparing two database schemas and generate changelogs automatically to bring one in sync with the other using "Liquibase diffChangeLog" command

Cons

diff and diffChangeLog commands are powerfu in Liquibase to make two database schema in sync but can produce noisy or incomplete results, especially when comparing across different database types or versions.
If two developers create changes with the same id in different files, Liquibase will throw a conflict even if they’re for different modules, along with this changelog files can become large and difficult to organize.
While Liquibase supports rollbacks, they often require manual intervention fgor complex changes for example in data migrations or multi-step schema changes, rollback logic can be hard to write and maintain.
Currently liquibase have less integration with IDE's like Intellij or VSCode which makes sometime hard to manage changesets and scripts

Likelihood to Recommend

Based on my experience so far on using Liquibase in my current project, I have seen that Liquibase changelogs are version control where multiple team members and developers can work together on database and deployed automatically via CI/CD Pipeline integration using github actions and it applies same changelogs to all enviroments to remain in sync and avoid any enviroment drift. Also as Liquibase stores changelog audits in DATABASECHANGELOG table it helps in tracking purposes and to easily rollback any change . Whereas in some scenarios I feel that Liquibase have some drawbacks where if complex transformation between tables is not optimized for bulk data operations which eventually degrades database performance.

Kunwarpreet Singh

Software Engineering Lead in Engineering at Optum (10,001+ employees)

Vetted Review

1 year of experience

Liquibase DB version control made easy

Rating: 10 out of 10

Incentivized

August 18, 2025

Use Cases and Deployment Scope

Liquibase for version control of both Oracle Databases (version 12c to 19c) and Postgres. We are pairing it with Gitlab and our use so far has been leaps and bounds better than any previous solution we have used in the past. Version control on databases is always a pain, but with Liquibase, it has helped our team of over a dozen developers be able to control, validate, and not break each other's work in ways that no other tool has been able to do yet.

Pros

Amazing Documentation
Easy integration with existing CI/CD pipelines
Tags and snapshots make rollback a breeze.

Cons

for Linux installer, add to the script to add to PATH for executable
Reduce noise on CLI header and show on verbose flag

Likelihood to Recommend

Any Codebase that does schema or table changes all the time for development or where Development and code is mostly in the database or SQL liquibase is a must.
In a codebase where the database is pretty static or is just a place to dump data, liquibase is probably too much.

You also need to have a team for it to really make sense. Doing a solo or small team project doing full version control on the database is probably more overhead than it is worth.

aaron motley

Cloud Network Engineer II in Information Technology at Allied National (51-200 employees)

Vetted Review

1 year of experience

Liquibase Pro Review

Rating: 9 out of 10

Incentivized

August 18, 2025

Use Cases and Deployment Scope

Our enterprise database had only one main code base for a long while. That code base was able to handle its own schema changes. However, as we have expanded, we now have multiple applications and services reading and writing to the database. It was no longer practical to use the original code base to manage schema changes. Liquibase has become our centralized schema-management system and has worked very well for us. It is flexible and extensible with a simple and effective design that makes changes easy to track for the DBA. If you are familiar with CLI, the learning curve is small. We now use it to track and apply changes across individual developer database instances, as well as for shared testing and production environments.

Pros

Liquibase tracks changes in a metadata table contained directly in the target database, making easy administration for the DBA.
Liquibase handles many validation tests out of the box, making it easy to choose which ones you want to include, with options for writing your own if you choose. This makes it robust and flexible in terms of validation before deployment.
Liquibase provides easy integration into deployment pipelines for CI/CD. We use it with GitHub for source control and Circle CI for validation and deployment pipelines.

Cons

One thing that is missing and really needed is tracking of how long a particular changeset took to apply. There is only one date stamp in the metadata table, and it reflects the end time of the changeset command. While most changes run in milliseconds, it is often crucial to know how long it took to create an index, or for a change that locks a table. Right now, I just have to monitor myself. In some cases I can do some rough math based on the Liquibase update report, but only on the run as a whole, not each individual change. Perhaps Liquibase could write a beginning entry to the DATABASECHANGELOG, with a begin time, and then update that entry with an end time when the command has finished.
The "One change per changeset" policy check isn't robust enough to be adequately used with Liquibase-formatted mySQL changelogs. In mySQL, you must drop and recreate stored logic objects. There is no ALTER option, so either the DROP and CREATE must go into the same changeset (triggering the policy check), or they must be managed in two changesets (meaning two to manage for each logical change). It seems a DROP and CREATE could be made a special case for this policy check.

Likelihood to Recommend

Our enterprise database had only one main code base for a long while. That code base was able to handle its own schema changes through a built-in ORM. However, we have added multiple applications and services that read and write to the database, and therefore need schema changes to the database as well. It was no longer practical to use the original code base to manage schema changes.

Liquibase has become our centralized schema-management system and has worked very well for us. It is flexible and extensible with a simple and effective design that makes changes easy to track for the DBA. If you are familiar with CLI, the learning curve is small. We now use it to track and apply changes across individual developer database instances, as well as for shared testing and production environments.

Stephanie Williams

Data Architect in Engineering at Munibilling (51-200 employees)

Vetted Review

View profile

My Experience using Liquibase

Rating: 8 out of 10

Incentivized

August 18, 2025

Use Cases and Deployment Scope

In a modernization effort for a federal client, we leveraged Liquibase to improve visibility and automation with the database deployments. We have multiple AWS Aurora PostgreSQL databases that have to maintain consistency through each environment. Liquibase helps us to track what data is in each environment and allows us to build once and deploy many. This has helped us to make a major improvement in transparency for our client while also building a consistent and repeatable process going forward as the databases get updated. We also are utilizing Liquibase for a database reconciliation effort to deploy changes into a newly created schema to reconcile data after a migration. Liquibase allows us to make these deployments which will normally take months to minutes. Truly enjoy the service.

Pros

Liquibase provides a clear error log that allows us to pinpoint what to troubleshoot.
The service does not deploy bad data, which helps us keep our databases clean.
Liquibase works with GitHub Actions as well as AWS Codebuild and AWS Lambda. The flexibility allows us to deploy the service in many different ways.

Cons

I would like Liquibase to explore all errors in the changelog files compared to one at a time. We spent a lot of time troubleshooting one error at a time versus having a batch log of errors in each file.
Understanding where to get support on things. I spent a lot of time researching externally to learn what the best practices were. Although I found some of the youtube videos helpful, I would like a little more of a technical support. This may be a feature with the paid tier, however, we leveraged open source.
Seeing more examples of how others use Liquibase and their usecases will be helpful. That way we can learn from each other which may help us improve on our own deployments.

Likelihood to Recommend

It is well suited for modernization efforts where there are multiple environments and lots of change. The service thrives in an area where there are technically sound engineers specifically in the infrastructure space who can deploy the service and troubleshoot. If a team has only DBA's who do not understand infrastructure side of house, this service will be a pain to stand up and could be even more of a pain to troubleshoot as there will be a knowledge gap between infrastructure and code deployment.

Marrsail Bailey

Technical Architect Specialist in Engineering at Accenture Federal Services (10,001+ employees)

Vetted Review

Verified on LinkedIn

Liquibase A Game-Changer for Reliable and Automated Database Deployments

Rating: 10 out of 10

Incentivized

August 16, 2025

Use Cases and Deployment Scope

We use Liquibase to manage database schema changes across environments in a controlled, versioned, and automated manner. It addresses business problems like inconsistent schema deployments, manual errors, and lack of traceability. Our use case includes CI/CD integration for automated rollouts, tracking changesets in source control, and ensuring database compliance and rollback capability for multiple Oracle and other DBs.

Pros

Version-Controlled Database Migrations
Rollback and Change Auditing
Environment-Agnostic Deployments with Contexts and Parameters

Cons

Learning Curve for XML/YAML Syntax and Tags

Likelihood to Recommend

CI/CD Pipeline Integration for Schema Changes

Verified User

Engineer in Engineering (10,001+ employees)

Vetted Review

2 years of experience

New Liquibase User

Rating: 10 out of 10

Incentivized

August 15, 2025

Use Cases and Deployment Scope

We have started to use Liquibase for managing non-production environments. This provides the ability to ensure that no developer changes are missed when refreshing lower environments

Pros

consistency in schemas
everyone is using the same method for deploying changes
ability to do comparison to ensure we know what we have deployed

Cons

too new to the product to make an accurate assessment at this time

Likelihood to Recommend

We have an Oracle database that is vendor supported and all changes come from them. The main schema for the vendor has given rise to lots of additional functionality that is implemented using additional schemas. We have started using Liquibase to do the changes for the additional schemas. This is not suitable for the vendor code at this time and that would be an area that Liquibase could partner with third-party vendors to support their code changes as well

Verified User

Employee in Information Technology (10,001+ employees)

Vetted Review

Useful Features of Liquibase

Rating: 10 out of 10

Incentivized

August 12, 2025

Use Cases and Deployment Scope

We use Liquibase to deploy schema changes to our databases. Liquibase addresses versioning issues with our schemas/databases. We use it on 2 databases. One which we own and another which has 2 schemas that we share with another team.

Pros

Versioning - it's easy to see change history of database schema
Deployments/Rollbacks - easy to make and undo changes

Cons

Better support for SQL changelogs. Not all features are available in SQL changelogs. SQL changelogs are easier to read

Likelihood to Recommend

Apply/rollback changes, view version history

Verified User

Contributor in Information Technology (10,001+ employees)

Vetted Review

5 years of experience

Top of the Line Database Release Management Tool

Rating: 7 out of 10

Incentivized

August 11, 2025

Use Cases and Deployment Scope

We group database SQL changes by ticket and release, performing managed deployment across environments. The SQL is entered into the GUI tool. Once the scripts are entered, everything is checked into Git using the plugin. Once in Git, Jenkins stages the artifacts to be deployed by Ansible AAP using Hammer libraries provided by Liquibase. Using this we can determine which tickets have been deployed, which need to be deployed, and which may have been modified after initial deployment through checksum comparison.

Pros

Grouping environment configurations and ordering the deployment into a pipeline.
Tagging by release, requirement grouping.
Supporting drivers for all our different databases such as Oracle, PostgreSQL, MySQL, Greenplum.

Cons

The Git integration is kind of non-intuitive with the different view, and then separate cloning and project import processes.
If a single database fails to connect or resolve with TNS, sometimes the whole pipeline locks down and won't accept changes.
Transactional boundaries need to be manually managed in Oracle if a deployment fails and requires human intervention.

Likelihood to Recommend

It's mainly good for application-driven deployment of database changes requested by developers such as new tables, new columns, triggers. The user GUI interface combined with the automation libraries allows for a number of people to be able to push changes without needing to setup the developer tool locally. In my opinion, it shouldn't be used for management of internal table data or System configuration of the database itself.

Verified User

Administrator in Information Technology (10,001+ employees)

Vetted Review

8 years of experience

Liquibase your great choice

Rating: 9 out of 10

Incentivized

August 7, 2025

Use Cases and Deployment Scope

We use Liquibase to automate deployments to all types of databases. It is very useful for deploying the same changes in different environments, recording everything that has been modified and, above all, being able to perform rollback and audit on uploads to production. We haven't encountered any issues so far. All of them have been resolved through the community or with the product's own documentation.

Pros

Keep a comprehensive record of changes
Facilitate rollbacks
Abstract the change of database type, achieving easy automation

Cons

Calculate the rollback automatically

Likelihood to Recommend

Liquibase is suitable for all the automatic database changes your organization wants to make.

Verified User

Engineer in Engineering (1001-5000 employees)

Vetted Review

3 years of experience

Loading Reviews List....

Liquibase Pro Review

Rating: 9 out of 10

Incentivized

August 18, 2025

Use Cases and Deployment Scope

Pros

Liquibase tracks changes in a metadata table contained directly in the target database, making easy administration for the DBA.
Liquibase handles many validation tests out of the box, making it easy to choose which ones you want to include, with options for writing your own if you choose. This makes it robust and flexible in terms of validation before deployment.
Liquibase provides easy integration into deployment pipelines for CI/CD. We use it with GitHub for source control and Circle CI for validation and deployment pipelines.

Cons

One thing that is missing and really needed is tracking of how long a particular changeset took to apply. There is only one date stamp in the metadata table, and it reflects the end time of the changeset command. While most changes run in milliseconds, it is often crucial to know how long it took to create an index, or for a change that locks a table. Right now, I just have to monitor myself. In some cases I can do some rough math based on the Liquibase update report, but only on the run as a whole, not each individual change. Perhaps Liquibase could write a beginning entry to the DATABASECHANGELOG, with a begin time, and then update that entry with an end time when the command has finished.
The "One change per changeset" policy check isn't robust enough to be adequately used with Liquibase-formatted mySQL changelogs. In mySQL, you must drop and recreate stored logic objects. There is no ALTER option, so either the DROP and CREATE must go into the same changeset (triggering the policy check), or they must be managed in two changesets (meaning two to manage for each logical change). It seems a DROP and CREATE could be made a special case for this policy check.

Likelihood to Recommend

Stephanie Williams

Data Architect in Engineering at Munibilling (51-200 employees)

Vetted Review

View profile