diff options
| author | Elrond <elrond+mediagoblin.org@samba-tng.org> | 2012-06-14 21:57:24 +0200 |
|---|---|---|
| committer | Elrond <elrond+mediagoblin.org@samba-tng.org> | 2012-06-14 21:57:24 +0200 |
| commit | b105540141ce3557456059b0e5dd5e589063e2f3 (patch) | |
| tree | 5f1edaf7ea848e660aef4ef141c707d9684fc8f9 /mediagoblin/tests/test_sql_migrations.py | |
| parent | 4ba4e27b4430f6f3ad5b75a209688830dea2bbf1 (diff) | |
| download | mediagoblin-b105540141ce3557456059b0e5dd5e589063e2f3.tar.lz mediagoblin-b105540141ce3557456059b0e5dd5e589063e2f3.tar.xz mediagoblin-b105540141ce3557456059b0e5dd5e589063e2f3.zip | |
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.
Diffstat (limited to 'mediagoblin/tests/test_sql_migrations.py')
0 files changed, 0 insertions, 0 deletions