Hi All,
I want our production systems to start caring about the versions of
their schemas. sqlalchemy-migrate was the first project I came across
which addresses this. What other projects should I look at in this area,
or is sqlalchemy-migrate the obvious choice?
If it is, how can I, in my
On May 17, 2010, at 1:13 PM, Chris Withers wrote:
Hi All,
I want our production systems to start caring about the versions of their
schemas. sqlalchemy-migrate was the first project I came across which
addresses this. What other projects should I look at in this area, or is
Michael Bayer wrote:
sqlalchemy-migrate is the obvious choice.I am also developing a micro-migrations system called Alembic (http://bitbucket.org/zzzeek/alembic)
If we start with sqlalchemy-migrate, do you reckon switching to Alembic
when it's mature would be feasible?
Chris
--
It's not clear that Alembic has real advantages over Migrate. Its simpler for
sure since it only is for SQLA 0.6 and up and doesn't attempt to do the crazy
things Migrate does like versioning SQLite databases. I'm going to attempt to
handle branching (but already that means, ugly hex digest
