-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Ignore columnDefinition in schema comparison #5224
Ignore columnDefinition in schema comparison #5224
Conversation
d003fd6
to
b799815
Compare
b799815
to
a49798b
Compare
a49798b
to
626eb67
Compare
Is this still WIP? |
Without digging too much into the details, the approach here looks more straightforward and correct than the one in #5234. So I assume if the test from there passes with this fix, this is what we need. |
…umnDefinition` is set When a `Column` is compared against another `Column` with a `$_columnDefinition`, it yields invalid results, because it generates a diff, but does not declare that the `columnDefinition` is the changed property. Before `3.3.1`, this behavior worked fine, but doctrine#5220 introduced a regression that led to the schema comparison changing behavior here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works for me and schema diff because of custom columnDefinition
are gone 👍
Blocked by #5239 |
Summary
Support schema validation when using
columnDefinition
.Closes #5234