Fix migrations reusing column objects #1081
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closes: gnocchixyz#1080 Related to: sqlalchemy/sqlalchemy#5669
unexceptable
force-pushed
the
bug/mysql_migration
branch
from
504cc30
to
18c135a
Compare
|
Cool, that seems to have fixed that. :) @chungg @tobias-urdin You able to review? |
|
Congrats! This looks good to me. |
jd
approved these changes
Nov 4, 2020
|
@Mergifyio backport stable/4.2 |
|
Command
|
|
@Mergifyio backport stable/4.4 stable/4.3 |
This was referenced Mar 29, 2021
|
Command
|
tobias-urdin
added a commit
that referenced
this pull request
Mar 29, 2021
Fix migrations reusing column objects (bp #1081)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes: #1080
Related to: sqlalchemy/sqlalchemy#5669