Update/upsert records should use patch - #146
Merged
Merged
Conversation
kriszyp
force-pushed
the
patch-on-update
branch
from
February 16, 2026 04:39
aa34963 to
9930de9
Compare
kriszyp
marked this pull request as ready for review
February 16, 2026 14:38
cap10morgan
approved these changes
Feb 17, 2026
DavidCockerill
approved these changes
Feb 18, 2026
This was referenced May 20, 2026
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
3 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.
This changes the behavior of our
updateoperation (andupsertwhen there is no existing record), to use apatchinstead of aputmethod, which more closely aligns with the intended semantics, preserving individual property updates in distributed conflicted data write scenarios.