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.
Liquibase 3.4.0 has been released and is working it’s way through the Maven mirrors.
I’ve moved the blog hosting off a wordpress server and am now hosting it on GitHub along with the rest of www.liquibase.org.
When I first released Liquibase as open source in 2006, Sourceforge was the obvious place to host the project. Over the years, however, I’ve been slowing shifting functionality off sourceforge to liquibase.jira.com, github.com/liquibase and this blog.
For people who have used Liquibase for a long time, a common question they have is how to clear out a changelog file that has gotten unwieldy.
Yes, I know 3.3.4 just came out yesterday, but there was a configuration issue that affected dependencies in Maven.