-
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
[GH-9807] Fix: initialize potentially empty collections at the hydration complete #9870
Conversation
Anybody alive here? 🙂 |
Please improve your commit message according to the contributing guide. |
3d7318b
to
7e462d2
Compare
Thanks for the comments @greg0ire, I've fixed it |
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.
I forgot to mention that in the contribution guidelines, but can you wrap the body of your commit message (which is great, good job!) at 72 chars?
Hm, do you mean leaving only the headline? 72 chars is not enough to unfold the reasoning |
No, I mean wrapping as in adding a linebreak when a line is 72 chars long. With vim properly configured, you can do that with |
Got it, thanks for the hint. I misunderstood "wrapping" for "reducing" |
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.
Good from my first review
If ObjectHydrator faces an empty row to an uninitialized collection, it initializes it, to prevent it from querying again (DDC-1526). However, if that row is the first but not the only in the collection, the next rows will be ignored, as the collection will be considered "existing", and "existing" collections are only replaced if REFRESH hint is present. To prevent it, we defer initialization to the end of the hydration. Fixes doctrineGH-9807
Thanks @popov-a-e ! |
Closes #9807