Feature: Table.upsert() #2203
Merged
Feature: Table.upsert() #2203
Conversation
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
… put operations for syncing the intent all the way to server.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As prematurely documented on the website: https://dexie.org/docs/Table/Table.upsert()
We need this for realm creation on sharing. Recommendations of creating realms from boundRealmId will be updated in docs to use Table.upsert() instead of Table.put() - since Table.put() replaces the existing owner of the realm while Table.upsert() only makes sure to get the object created with some props but leaving owner property unchanged.