
On 6/28/19 2:59 PM, Aaryan Bhagat wrote:
I will explain a little bit more what I exactly did, I downgraded alembic to
2d2d0ef0828f
version, made changes to58858f75303c
migration file and then tried to upgrade again but alembic is recognising duplicating columns which means it has not downgraded properly, can we somehow erase all changes keep till2d2d0ef0828f
version somehow cleanly?
Pointers on this are required.
It's not alembic's fault. It's sqlite which can't remove a column. You have to test for things like this. There are examples in the existing migrations such as 46e92facee7_add_serverowner_domainowner.py.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan