Details
-
Improvement
-
Resolution: Done
-
Major - P3
-
None
-
None
Description
While investigating how Timestamp types are structured and compared for DOCS-9384, we also looked at ObjectID, which is compared in byte order with memcmp().
While the BSON spec states that "Each type must be serialized in little-endian format", it's clear that an ObjectID's components must actually be stored in big endian, with the most significant bytes appearing first in the byte sequence.
The following pages should be updated to clarify this:
Attachments
Issue Links
- is related to
-
DOCS-9384 BSON spec conflicts with documentation over Timestamp structure
-
- Closed
-
-
SERVER-6054 Improve uniqueness of ObjectIds
-
- Backlog
-
- links to