SchemaDiff detecting errors in column definition when using custom type in 4.0.x #5988
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
|
Thank you. I think, the issue that is tested here is not specific to MySQL. Can we please move it to a function test that is executed on all platforms (e.g. Also, please run |
…pe in 4.0.x Co-authored-by: Alexander M. Turek <me@derrabus.de>
derrabus
force-pushed
the
try-column-custom-type-diff-over-v4
branch
from
5a2dab7
to
5015338
Compare
derrabus
approved these changes
Jun 15, 2023
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.
Summary
Added test to prove it got fixed in 4.0.x. Original issue.