[DOCS-14228] Clarify the semantics of `updatedExisting` in the findAndModify command Created: 15/Feb/21 Updated: 30/Oct/23 Resolved: 28/Oct/21 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Kaloian Manassiev | Assignee: | Ian Fogelman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | docs-server-onboarding, quick-win | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 2 years, 15 weeks ago |
| Epic Link: | DOCSP-11701 |
| Story Points: | 2 |
| Description |
DescriptionThe documentation for the updatedExisting field of the findAndModify response, doesn't clearly indicate that updatedExisting will be set to true even if the query predicate matched, but the update operation resulted in no actual write (no-op write). We should update the documents to say: Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 27/Oct/21 ] |
|
Author: {'name': 'ian fogelman', 'email': 'ian.fogelman@mongodb.com', 'username': 'ianf-mongodb'}Message: |
| Comment by Githook User [ 27/Oct/21 ] |
|
Author: {'name': 'ian fogelman', 'email': 'ian.fogelman@mongodb.com', 'username': 'ianf-mongodb'}Message: |
| Comment by Githook User [ 27/Oct/21 ] |
|
Author: {'name': 'ian fogelman', 'email': 'ian.fogelman@mongodb.com', 'username': 'ianf-mongodb'}Message: |
| Comment by Githook User [ 27/Oct/21 ] |
|
Author: {'name': 'ian fogelman', 'email': 'ian.fogelman@mongodb.com', 'username': 'ianf-mongodb'}Message: |
| Comment by Githook User [ 27/Oct/21 ] |
|
Author: {'name': 'ian fogelman', 'email': 'ian.fogelman@mongodb.com', 'username': 'ianf-mongodb'}Message: |