Definitely agree. I use liquibase so that I can check database migrations into source control and have an easy way for other developers to update to the new sch

Definitely agree. I use liquibase so that I can check database migrations into source control and have an easy way for other developers to update to the new schema without having to understand a whole lot. It also provides a nice way to drop your whole database and recreate it if you need to. In addition, much like how unit tests force you to think about how to write code, rollbacks help when writing schema migrations to make sure that something could be undone if necessary. In practice, I've rarely used them though, and if you do it's likely going to be on a dev/staging server.