Bugfix release Liquibase 3.4.2 is now available from liquibase.org/download and through the Maven repositories.
Halloween–the spookiest night of the year. Spookiest night for those who don’t do production deployments anyway…
There were 136 responses to the 2015 Liquibase Survey. Since I’m relying on self-selection for people answering the survey, the first question is how representative is the data. The only two “demographic” survey questions I have alternate data points for are version used and country.
Early on, Liquibase only supported XML changelogs with each changeSet listed in it. There are many advantages to using that setup, but there are now many different ways to store your database changes.
If you missed last month, I’ve started a monthly status post to give a better window into Liquibase development and the Liquibase community. I’d appreciate any feedback you have on how helpful (or not) it is and/or any suggestions you have.
One problem with running an open source project is that we don’t really have “customers” to contact for feedback and product suggestions. I can always just add features that I think make sense, but one thing I’ve learned is that people use Liquibase in amazing ways I would never have imagined.
This is the first in a planned monthly post designed to give a better window into Liquibase development and the Liquibase community. I’d appreciate any feedback you have on how helpful (or not) it is and/or any suggestions you have.
Bugfix release Liquibase 3.4.1 is now available from liquibase.org/download and through the Maven repositories.
Once you’ve created a database changelog file, what is the best way to run it? As always, it depends on what works best for you. There are three main ways to run Liquibase: “automatically on startup”, “manually as needed”, or “Just give me the SQL and I’ll do it myself”. All three work with any changelog file, so use the method (or combination of methods) which works best for your project.
There are many, many different processes and requirements companies have for managing their database schemas. Some allow the application to directly manage them on startup, some require SQL scripts be executed by hand. Some have schemas that can differ across customers, some have only one database to deal with.