Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-12302

Breaking Change: Timestamp(0,0) now replaced on insert

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor - P4
    • Resolution: Works as Designed
    • 2.4.8
    • None
    • None

    Description

      > db.test.drop()
      true
      > db.test.insert({ "NumberInt" : NumberInt(0), "Timestamp" : Timestamp(0, 0) })
      > db.test.insert({ "Timestamp" : Timestamp(0, 0) })
      > db.test.find()
      { "_id" : ObjectId("52cdf6870449e37d1e934214"), "NumberInt" : 0, "Timestamp" : Timestamp(0, 0) }
      { "_id" : ObjectId("52cdf6890449e37d1e934215"), "Timestamp" : Timestamp(1389229705, 1) }
      >

      This causes things like the Timestamp not round tripping correctly doing a dump restore from 2.4 to 2.5 (this bug does not exist in 2.5)

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              sverch Shaun Verch
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: