You’ve just run a
liquibase update. Moments later, your stomach churns as you realize that there were some big mistakes in the changes you just deployed and your database is definitely not in the state you intended. What do you do now?
Don’t panic. You’ve got options.
It’s an exciting time for the Liquibase community. The latest release, 3.7, has over 350 commits from the community and from Datical. Datical has dedicated several engineers to the Liquibase open source project. Most recently, these efforts helped push the Liquibase 3.7 release with several important new features including improved support for PostgreSQL, DB2, MariaDB, MS SqlServer, Ingres, and Firebase, and much more.
Last year, we invited the Liquibase community to take a survey to help us understand how Liquibase is used and how we can improve. A small sample size from our community (a little over 200 people out of 4M+ downloads in the past 12 months) participated via the Liquibase.org website. Here’s what we learned.
We have reviewed and accepted pull requests for extensions that add and enhance support for Hibernate and HANA. Hibernate is one of the most popular Java ORMs and SAP HANA powers critical ERP, CRM, and SRM systems.
As many of you know, a few years after starting the Liquibase open-source project, I joined the team at Datical. For those who are unaware, Datical is a commercial solution built on top of Liquibase. Datical is also the primary maintainer of the Liquibase open source project - though we are always looking for more engaged community members who might be interested in being stewards to the project along with me. While I’ve enjoyed the years of growth - both Liquibase and Datical have seen, I had always hoped for a better transition from the open-source project I founded to the commercial software that I now help architect. Finally, the wait is over – and I’m tremendously excited to announce that Datical’s latest release supports users bringing in their own XML changesets and changelogs from Liquibase.