3 ms·
Sqitch is a pretty useful migration tool: http://sqitch.org http://sqitch.org
by Cieplak 9y ago
Sqitch is a pretty useful migration tool:
http://sqitch.org http://sqitch.org
- sbuttgereit 9y agoI like the whole sqitch approach much better than that provided by most migrations (if I'm in migration land, I use https://flywaydb.org/ https://flywaydb.org/). From the version control perspective you get the sprawl of changes across files like you do with migrations. I find that, for tables, if I write anonymous "DO" blocks in a single script to manage both the initial creation of the table and any later deltas, I get a very satisfactory version control history. This is a bit different than the recommended approach (if I'm not mistaken). I just wish it wasn't written in perl with 10,000 cpan dependencies which may or may not build in a given circumstance.
- oneweekwonder 9y agoAnother options is liquibase[0]. I use the diff[1] tool to create a changeset and then convert it to sql before applying it to my db. liquibase keeps a log and lock table in your db so you can always review the changeset you applied to the db at a later time. [0] http://www.liquibase.org/ http://www.liquibase.org/ [1] http://www.liquibase.org/documentation/diff.html http://www.liquibase.org/documentation/diff.html
- trampi 9y agoLiquibase is definitifely a good recommendation. We use it to update Oracle, postgreSQL, MariaDB as well as exporting the current schema as a hsqldb-script. Some migrations are only executed for some of our customers.
- robertlagrant 9y agoAlso a big fan of Liquibase here, on SQL Server. I've used Redgate in the past, which is even graphical etc, so simpler to use for slightly less technical DBAs.