Specify aggregate and event database insertion order#469
Merged
erikrozendaal merged 4 commits intomasterfrom May 12, 2025
Merged
Specify aggregate and event database insertion order#469erikrozendaal merged 4 commits intomasterfrom
erikrozendaal merged 4 commits intomasterfrom
Conversation
When inserting multiple rows it is important that all inserts happen in a consistent order, otherwise multiple concurrent transactions can deadlock. Also ensure newly inserted events have a correct sequence number so that a primary key constraint violation is raised when multiple concurrent transactions update the same aggregate, which will result in a Sequent optimistic locking error.
lvonk
reviewed
May 12, 2025
lvonk
reviewed
May 12, 2025
This was the important bit...
This results in a more efficient execution plan.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When inserting multiple rows it is important that all inserts happen in a consistent order, otherwise multiple concurrent transactions can deadlock.
Also ensure newly inserted events have a correct sequence number so that a primary key constraint violation is raised when multiple concurrent transactions update the same aggregate, which will result in a Sequent optimistic locking error.