[DOCS-2589] GLE updatedExisting and upserted fields Created: 24/Jan/14 Updated: 28/Jan/14 Resolved: 28/Jan/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.0, mongodb-2.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jeremy Mikola | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 10 years, 3 weeks, 1 day ago |
| Description |
|
The documentation refers to updateExisting, but the field is actually updatedExisting. In MongoDB 2.4.x, upserted is only present in the GLE response if the update did not already include an _id field. In 2.5.x, it appears to always be included (if updatedExisting is false, that is), but it may not always be an ObjectId. It could very well be the existing _id that was in the update criteria for the upserted document. |
| Comments |
| Comment by Githook User [ 28/Jan/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |