[SERVER-39060] Provide a way to perform an upsert in the Stitch Support Library Created: 17/Jan/19 Updated: 29/Oct/23 Resolved: 28/Jan/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.8 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Justin Seyster | Assignee: | Justin Seyster |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Query 2019-01-28, Query 2019-02-11 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Stitch needs a way to see the result of an update operation that finds no document and so has to create a new document based on the query and update document (an upsert). One possibility is modifying stitch_support_v1_update_apply() so that it uses upsert behavior when the 'documentBSON' argument is NULL. |
| Comments |
| Comment by Githook User [ 28/Jan/19 ] |
|
Author: {'username': 'jseyster', 'email': 'justin.seyster@mongodb.com', 'name': 'Justin Seyster'}Message: |