We used this back when I worked in Brazil. Liquibase is fine and solved some of our problems keeping schema migrations in sync across developers, but I remember

We used this back when I worked in Brazil. Liquibase is fine and solved some of our problems keeping schema migrations in sync across developers, but I remember it lacked some essential features such as syntax correction. I remember I wrote a couple of Ruby scripts to check things for me. The catch phrase is unfortunate, because it could trick one to think this backs your data. This is basically a Rails migrations like solution that relies on XML files to describe changes to your schema. Update: And now JSON even. Hoorray.