Skip to content
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

Make Table::removeUniqueConstraint() actually work #4667

Merged

Conversation

hschletz
Copy link
Contributor

@hschletz hschletz commented Jun 6, 2021

Q A
Type bug
BC Break no
Fixed issues

Summary

Table::removeUniqueConstraint() used the wrong method (hasForeignKey()) instead of hasUniqueConstraint() to check for existing unique constraint, causing removeUniqueConstraint() to fail unconditionally.

Also adding tests for removeUniqueConstraint().

greg0ire
greg0ire previously approved these changes Jun 6, 2021
SenseException
SenseException previously approved these changes Jun 6, 2021
Table::removeUniqueConstraint() used the wrong method (hasForeignKey())
instead of hasUniqueConstraint() to check for existing unique
constraint, causing removeUniqueConstraint() to fail unconditionally.

Also adding tests for removeUniqueConstraint().
@greg0ire greg0ire force-pushed the fix-removeUniqueConstraint-wrong-method branch from fc3e68c to 0e398ec Compare June 6, 2021 20:53
@greg0ire greg0ire added this to the 3.1.1 milestone Jun 6, 2021
@greg0ire greg0ire merged commit 7ef2a33 into doctrine:3.1.x Jun 6, 2021
@greg0ire
Copy link
Member

greg0ire commented Jun 6, 2021

Thanks @hschletz !

88.32% (+0.52%) compared to b5c2979

Nice ! 🙂

@hschletz hschletz deleted the fix-removeUniqueConstraint-wrong-method branch June 18, 2021 16:04
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants