Skip to content

ObjectId plans beyond 2106 #1440

Open
Open
@midnight-wonderer

Description

@midnight-wonderer

Hi, we are probably dead by then, but I wonder what is the plan beyond 2106?

 
As you may know, ObjectId will overflow on February 7, 2106; there are a couple of ways forward then.

  • extend ObjectId by 1 byte
  • do nothing, using the current specification, and let it overflow into 1970.

 
These impact how we design the schema now, as we can either:

  • simply store ObjectId if the plan is to extend the timestamp portion of ObjectId
  • store ObjectId and time as separate fields, and never use ObjectId as time

 
What do you say?

P.S. BTW, the specification is currently incorrect; the ObjectId will overflow in Feb, not in Jan.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions