Skip to content

graph: Allow remove followed by remove in write batches #5940

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

Merged
merged 1 commit into from
Apr 11, 2025

Conversation

lutter
Copy link
Collaborator

@lutter lutter commented Apr 10, 2025

If subgraphs delete entities without checking if they exist, we get two removes in a row. In the database, the second remove would just lead to a query that changes nothing. We'll do the same when putting a write batch together.

Fixes #5449

If subgraphs delete entities without checking if they exist, we get two
removes in a row. In the database, the second remove would just lead to a
query that changes nothing. We'll do the same when putting a write batch
together.

Fixes #5449
@lutter lutter requested a review from zorancv April 10, 2025 16:52
Copy link
Contributor

@zorancv zorancv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense!

@lutter lutter merged commit 17360f5 into master Apr 11, 2025
6 checks passed
@lutter lutter deleted the lutter/extra-remove branch April 11, 2025 21:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] Impossible combination of entity operations
2 participants