Uploaded image for project: 'Go Driver'
  1. Go Driver
  2. GODRIVER-1092

Timestamp in ObjectID is stored as uint32

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • BSON
    • None

    Description

      It seems that the 'time' component of primitive.ObjectID is stored in the first 4 bytes of the ObjectID. Will this not be a problem when we reach 2038?
      I realise that expanding to an int64 would likely not be an option in a slice of 12 bytes, but if it can't be fixed, should it at least not be emphasised in the docs?

       

      Attachments

        Activity

          People

            divjot.arora@mongodb.com Divjot Arora (Inactive)
            chan58 Chris Hansen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: