First migration fix: commit after each migration.
authorElrond <elrond+mediagoblin.org@samba-tng.org>
Thu, 14 Jun 2012 19:57:24 +0000 (21:57 +0200)
committerElrond <elrond+mediagoblin.org@samba-tng.org>
Thu, 14 Jun 2012 19:57:24 +0000 (21:57 +0200)
commitb105540141ce3557456059b0e5dd5e589063e2f3
tree5f1edaf7ea848e660aef4ef141c707d9684fc8f9
parent4ba4e27b4430f6f3ad5b75a209688830dea2bbf1
First migration fix: commit after each migration.

sqlite doesn't like complex changes (alter table) to happen
inside a transaction that has already done other things.
And really, each migration should say "I'm done" and commit
its changes.

This is not the full story, but it's the core of it.

Specifially the migration framework should probably do a
rollback "just in case" after each migration.
mediagoblin/db/sql/migrations.py