-
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
Failed getting entity with fetch eager property #11090
Merged
greg0ire
merged 5 commits into
doctrine:2.19.x
from
dbannik:2.17.x-failed-getting-entity-with-fetch-eager
Mar 16, 2024
Merged
Failed getting entity with fetch eager property #11090
greg0ire
merged 5 commits into
doctrine:2.19.x
from
dbannik:2.17.x-failed-getting-entity-with-fetch-eager
Mar 16, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dbannik
force-pushed
the
2.17.x-failed-getting-entity-with-fetch-eager
branch
2 times, most recently
from
November 28, 2023 21:12
a34f0d7
to
5bf5c5a
Compare
dbannik
commented
Dec 1, 2023
dbannik
added a commit
to dbannik/orm
that referenced
this pull request
Feb 13, 2024
…tion has not yet fully completed on eagerLoadCollections
dbannik
force-pushed
the
2.17.x-failed-getting-entity-with-fetch-eager
branch
from
February 13, 2024 11:15
39ea503
to
9a20452
Compare
test passed. please check my fix |
dbannik
added a commit
to dbannik/orm
that referenced
this pull request
Feb 15, 2024
…tion has not yet fully completed on eagerLoadCollections
…tion has not yet fully completed on eagerLoadCollections
greg0ire
force-pushed
the
2.17.x-failed-getting-entity-with-fetch-eager
branch
from
February 16, 2024 10:21
9a20452
to
e5e3166
Compare
… exploration, and we only need the regression test.
beberlei
previously approved these changes
Mar 16, 2024
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 didn't think about this case when working on #8391
The test and fix are valid.
I cleaned it up a little.
greg0ire
approved these changes
Mar 16, 2024
derrabus
changed the title
[2.17.x] Failed getting entity with fetch eager property
Failed getting entity with fetch eager property
Mar 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here, I provided tests for reproduction but without the solution to the problem itself.
Diff WithoutFetchEager\AbstractRemoveControl and WithFetchEager\AbstractRemoveControl