|
Planning to close this as a duplicate of SERVER-46389.
|
|
When you convert this message to structured logging, just log the Date_t without any stringification call, and let the logging subsystem handle it.
|
|
This code still exists. This could be an easy change to something that may confuse users.
|
|
When a Date_t represents a date before the epoch, Date_t::toString() writes out Date(<a negative integer number of milliseconds>), while dateToISOStringLocal looks like it depends on the behavior of libc on the system in question.
|
|
That is my sentiment as well.
How does the default Date_t::toString output compare with dateToISOStringLocal output?
|
|
milkie, when logging I think we pretty much always should just stream the Date_t object into the log, and let its own toString() implementation sort it out. That is, there should be no calls to dateToISOStringUTC or dateToISOStringLocal in logs. It looks like repl is the only code that needs changing, in any event.
|
Generated at Thu Feb 08 04:09:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.