-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[2.19.x] Fetching entities with Composite Key Relations and null values #11506
[2.19.x] Fetching entities with Composite Key Relations and null values #11506
Conversation
23e197d
to
a22feed
Compare
Please squash both commits and use a summary of the description of #11486 . This should be understandable with the git log alone. |
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.
Code-wise, I think it looks good, since no existing tests are changed. If it turns out this is useful, we will revert and ask people to add tests to protect their weird use cases.
917163d
to
ceeccb2
Compare
@greg0ire thanks, squashed, rebased and force-pushed now. |
Can you please amend your commit message to include a summary of the description? |
More on this in the contributing guide. |
ceeccb2
to
7201c0e
Compare
Remove redundant condition to check if target class contains foreign identifier in order to allow fetching a null for relations with composite keys, when part of the key value is null.
7201c0e
to
96d13ac
Compare
@greg0ire thanks, pushed now, hope it makes sense. |
Thanks @michalbundyra ! |
Yes, it should get merged up at some point. When that happens, maybe we will have to look at your PR to resolve conflicts/adapt the code, or maybe not and then you can rebase and improve things. |
Changes from #11486 into 2.19.x