updated upsert example response and option #40658
Closed
+46
−26
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.
updates the upserting into tables with constraints example to show the correct response, and adds the missing onConflict option to the return-the-exact-number-of-rows example.
i have read the contributing.md file:
yes
what kind of change does this pr introduce?
docs update
what is the current behavior?
the upsert docs show an incorrect response example and the second example is missing the onConflict option.
what is the new behavior?
the first example shows the correct response, and the second example includes the onConflict option so both examples match expected behavior.
additional context:
fixes #40653