On 8/3/15 6:51 PM, Mike Bayer wrote:
On 8/3/15 4:59 PM, Dirk Makowski wrote:
Hi all,
after upgrading alembic to 0.7.7 and SQLAlchemy to 1.0.8, when I try
to downgrade one step from head, I get the below KeyError. The
allegedly missing key is the revision ID of head. It is correctly
On 8/3/15 4:59 PM, Dirk Makowski wrote:
Hi all,
after upgrading alembic to 0.7.7 and SQLAlchemy to 1.0.8, when I try
to downgrade one step from head, I get the below KeyError. The
allegedly missing key is the revision ID of head. It is correctly
stored in the alembic table, and the file and
On 8/3/15 7:02 PM, Mike Bayer wrote:
On 8/3/15 6:51 PM, Mike Bayer wrote:
On 8/3/15 4:59 PM, Dirk Makowski wrote:
Hi all,
after upgrading alembic to 0.7.7 and SQLAlchemy to 1.0.8, when I try
to downgrade one step from head, I get the below KeyError. The
allegedly missing key is the
I had do revert back to alembic 0.6.7 for the down-migration to work again
(upgraded today from 0.6.6). Please find attached the bare scripts.
On Monday, August 3, 2015 at 11:27:40 PM UTC+2, Michael Bayer wrote:
can you confirm no issue with Alembic 0.7.6?Can you please send along
all
can you confirm no issue with Alembic 0.7.6?Can you please send
along all of your migration scripts; feel free to erase everything but
the version headers and empty upgrade() / downgrade() functions, I just
need to see the structure you're working with. thanks.
On 8/3/15 4:59 PM, Dirk
Hi all,
after upgrading alembic to 0.7.7 and SQLAlchemy to 1.0.8, when I try to
downgrade one step from head, I get the below KeyError. The allegedly
missing key is the revision ID of head. It is correctly stored in the
alembic table, and the file and its predecessor are also present.
Other
