Update does not ensure an _id field

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • 2.5.5
    • Affects Version/s: None
    • Component/s: Storage, Write Ops
    • None
    • Fully Compatible
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Scott Hernandez (Inactive)
              Reporter:
              Scott Hernandez (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: