-
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
Fixes #4252 Cascading refresh to lazy loaded assocations #6798
Fixes #4252 Cascading refresh to lazy loaded assocations #6798
Conversation
4d24521
to
c7cde75
Compare
@Netiul please change the destination branch to |
9d21362
to
9d9f684
Compare
@lcobucci 👍 Fixed that. |
9c46970
to
08a1e79
Compare
@FrankGiesecke |
616a168
to
01f89a8
Compare
f7f7511
to
01f89a8
Compare
Any news regarding this issue? I'm facing the same problem as I have to manually refresh the Collection as mentioned in this post. |
I have the same problem, cascade={"refresh"} declaration, refresh only parent entity from oneToMany relation. |
I am also facing this issue. This is probably not the best solution, but current workaround I use is:
|
News on this? |
e94e354
to
b4bd3ee
Compare
71879f1
to
61039f3
Compare
Rebased on 2.11.x |
61039f3
to
3b12f46
Compare
91053aa
to
52db072
Compare
…o toMany associations are not reset to empty collections
52db072
to
17bc1ad
Compare
There hasn't been any activity on this pull request in the past 90 days, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 7 days. |
I believe it's still relevant |
Looks like this was handled in #10065 🙂 |
Fixes #4252
Closes #1218
Bug description
Refreshing an entity resets toMany (extra) lazy loaded associations to an empty collection before the refresh operation is cascaded to its underlying associations. Meaning objects that should be refreshed stay unrefreshed in the UoW.
Fix
The fix simply cascades the operation to its associations before refreshing the current entity.