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.

Sign up for GitHub

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

Jump to bottom

Handle orphan removals and inverse removals gracefully when no dirty tracking is available #639

Open
beikov opened this issue Aug 4, 2018 · 0 comments
Open

Handle orphan removals and inverse removals gracefully when no dirty tracking is available #639

beikov opened this issue Aug 4, 2018 · 0 comments
Assignees
@beikov
Labels
component: updatable-entity-view kind: enhancement

Comments

@beikov
Copy link
Member

beikov commented Aug 4, 2018

Our orphan removal and inverse removal strategies currently depend on the initial state being available. When using the FULL flush mode, we do not do dirty tracking currently. Either we enable dirty tracking even then, which is simple, or we implement some kind of loading before update which is pretty complicated to do efficiently.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@beikov beikov

Labels
component: updatable-entity-view kind: enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@beikov