-
Notifications
You must be signed in to change notification settings - Fork 14.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hack around the "last migration doesn't stamp" Alembic bug #967
Conversation
a20e0b5
to
e1d066c
Compare
This makes MySQL, Sqlite and Postgres work with a special hard coded rule. I'm hoping Alembic fixes the root cause eventually.
e1d066c
to
0378841
Compare
Commit cite Postgresql but you are not doing anything specific for it. |
Postgres was working with the current default setup. Though I might want to run the |
@mistercrunch |
A'ight done, I referenced the new location of the DB as well |
* feat: add dropGroupByControl * control rename to DndColumnSelectControl * add DND feature flag * wip * fix lint * duplicate dnd control
* feat: add dropGroupByControl * control rename to DndColumnSelectControl * add DND feature flag * wip * fix lint * duplicate dnd control
* feat: add dropGroupByControl * control rename to DndColumnSelectControl * add DND feature flag * wip * fix lint * duplicate dnd control
* feat: add dropGroupByControl * control rename to DndColumnSelectControl * add DND feature flag * wip * fix lint * duplicate dnd control
This makes MySQL, Sqlite and Postgres work with a special hard coded
rule. I'm hoping Alembic fixes the root cause eventually.
@bkyryliuk