Greetings,
The BSON Timestamp type, documented here, includes a 32-bit time_t field. Could you please clarify whether this field is signed or unsigned? If signed, it will roll over on January 19, 2038 (the Y2038 issue). If unsigned, it will not roll over until 2106.
I understand that BSON Timestamp is intended for internal use only, as noted in the documentation. However, I am concerned that a signed time_t could cause internal rollover issues in MongoDB itself or impact any applications that happen to use this type directly.
Thank you for your time and insights,
John Lange
Founder & CEO, Y2038.com LLC