| commit | 4c77f3d56396a78f2708e59b9cb6c8f150b39b6d | |
| author | Jessica Tallon <tsyesika@tsyesika.se> | |
| Wed, 20 Jan 2016 09:09:42 +0000 (20 09:09 +0000) | ||
| committer | Jessica Tallon <tsyesika@tsyesika.se> | |
| Wed, 20 Jan 2016 09:09:42 +0000 (20 09:09 +0000) | ||
| tree | 64e3d57ab1c0b63a0413c395c61930d7ee794dfe | treesnapshot (tar.gz zip) |
| parent | 8de5a9319ae7553169fb51d368c5366d6f54fe14 | commitdiff |
Fix #5398 and #5395 - Fix tests failing due to problem creating connection for alembic
For some reason the alembic connection wasn't seeing any tables that existed
however the existing connection works well and we shouldn't be creating a brand
new one when we have one ready to use. I've used a little bit of a hack due to our
old version of alembic.
After 0.7.5 of alembic it offers a `Config.attributes` dictionary which is designed to
allow you to pass your connection/engine/whatever to the env.py config script so you're
not required to create new ones. As we're on an older version I just create a dictionary
with the same name and use it as otherwise documented. It seems this is the suggested
fix for #5395 and it fixes #5398 too.
For some reason the alembic connection wasn't seeing any tables that existed
however the existing connection works well and we shouldn't be creating a brand
new one when we have one ready to use. I've used a little bit of a hack due to our
old version of alembic.
After 0.7.5 of alembic it offers a `Config.attributes` dictionary which is designed to
allow you to pass your connection/engine/whatever to the env.py config script so you're
not required to create new ones. As we're on an older version I just create a dictionary
with the same name and use it as otherwise documented. It seems this is the suggested
fix for #5395 and it fixes #5398 too.
| mediagoblin/db/migration_tools.py | diffblobblamehistory | |
| mediagoblin/db/migrations/env.py | diffblobblamehistory |