Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DESCRIBE EXTENDED date format should be non-ambiguous #2002

Closed
rmoff opened this issue Oct 5, 2018 · 0 comments
Closed

DESCRIBE EXTENDED date format should be non-ambiguous #2002

rmoff opened this issue Oct 5, 2018 · 0 comments
Assignees

Comments

@rmoff
Copy link
Member

rmoff commented Oct 5, 2018

Currently DESCRIBE EXTENDED uses an ambiguous date format for last-message:

Local runtime statistics
------------------------
messages-per-sec:     50.30   total-messages:      5012     last-message: 10/5/18 9:54:06 AM UTC

Is this 10th May, or 5th October?!

I suggest we use a standard like https://en.wikipedia.org/wiki/ISO_8601 so:

2018-10-05T10:15:23+00:00

or at the very minimum, 2018-10-05 for the date portion of the timestamp

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants