[DOCS-9678] Timestamp is not a signed 64-bit integer Created: 20/Dec/16 Updated: 11/Jan/17 Resolved: 21/Dec/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | bsonspec |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Luke Lovett | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 7 years, 8 weeks ago | ||||
| Description |
|
The grammar in the BSON specification claims that the Timestamp type (0x11) is a signed 64-bit integer. In fact, a Timestamp is two unsigned 32-bit integers (time and increment, respectively), concatenated, effectively making Timestamp a 64-bit unsigned integer. This should be corrected on bsonspec.org. The MongoDB docs on Timestamp do not claim that timestamp is signed, so no change is needed: https://docs.mongodb.com/manual/reference/bson-types/ Pull request: https://github.com/mongodb/bsonspec.org/pull/46 |
| Comments |
| Comment by Kay Kim (Inactive) [ 21/Dec/16 ] |
|
merged! |