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

Throw on invalid one to one #10667

Merged
merged 1 commit into from
May 3, 2023
Merged

Conversation

greg0ire
Copy link
Member

@greg0ire greg0ire commented May 2, 2023

One to one relationships are not allowed to define a join column. That should be done on the owning side of the relationship.

@greg0ire
Copy link
Member Author

greg0ire commented May 2, 2023

@mpdude please review

Copy link
Member

@SenseException SenseException left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now, that this isn't a deprecation anymore and an unacceptable configuration that leads to an exception, shouldn't it get a test?

mpdude
mpdude previously approved these changes May 3, 2023
One to one relationships are not allowed to define a join column. That
should be done on the owning side of the relationship.
@greg0ire
Copy link
Member Author

greg0ire commented May 3, 2023

@SenseException I added a test :)

@greg0ire greg0ire added this to the 3.0.0 milestone May 3, 2023
@greg0ire greg0ire merged commit d075f5d into doctrine:3.0.x May 3, 2023
@greg0ire greg0ire deleted the throw-on-invalid-oto branch May 3, 2023 21:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants