[SERVER-12334] Update does not ensure an _id field Created: 11/Jan/14  Updated: 28/Oct/15  Resolved: 27/Jan/14

Status: Closed
Project: Core Server
Component/s: Storage, Write Ops
Affects Version/s: None
Fix Version/s: 2.5.5

Type: Improvement Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: Scott Hernandez (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-12523 When creating collection with autoInd... Closed
Related
related to SERVER-8237 autoIndexId:false should be disabled Closed
related to SERVER-12331 Insert creates the _id field, always Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

Just as insert now always creates an _id field, update should do the same to be consistent. See SERVER-12331 as guide.

Currently update only creates/requires an _id field if there is an _id index. It seems we should now ensure an the _id field for each updated document modified/inserted.



 Comments   
Comment by Githook User [ 27/Jan/14 ]

Author:

{u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}

Message: SERVER-12334: ensure _id field after update
Branch: master
https://github.com/mongodb/mongo/commit/e6c3c69c508b431a1c38dc5011928e236ddb09df

Generated at Thu Feb 08 03:28:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.