Migrating databases: Alembic vs. Liquibase, Flyway, ??

[Don Dwiggins]

I'm gradually working toward getting serious about controlled DB
migration (version control for DBs), and have been following the Alembic
announcements with interest. (We're already using SA successfully in a
Twisted environment, just making sure that all DB access is encapsulated
in deferreds.)

Recently, I came across mention of two projects that look similar:
Liquibase (http://www.liquibase.org/index.html) and Flyway
(http://flywaydb.org/). Both of them look to be based on Java, but that
aside, I'd be interested to know how they compare in terms of features,
maturity, etc.

Thanks for any info,
--

Don Dwiggins
Advanced Publishing Technology

[ne...@powertofly.com]

I will give you one very good reason to go with liquibase - technology independence. 

Alembic ties your db management to python and besides requires more manual work.

Say tomorrow you decide to have multiple services implemented in different languages, alembic is not going to cut it.

Just my 2cents since debating over the same issue. 

[Michael Bayer]

last I checked, XML was still a language.

--
You received this message because you are subscribed to the Google Groups "sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+...@googlegroups.com.
To post to this group, send email to sqlal...@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.

[Robert Grant]

Yeah, bringing up Python as a "technology independence" problem seems bizarre. When supporting SQLAlchemy (The Database Toolkit for Python), it seems as though Python is a smaller problem than Java and XML.