Please put the year first. Like, 2019-01-11 - 6:14AM
I would second this only because the mm/dd/yyyy format can be confusing to our members in other countries, who use dd/mm/yyyy. The format yyyy/mm/dd is unambiguous and puts things in their proper MSB-to-LSB order. OTOH, the format dd Mon yyyy is also okay, where Mon is the alpha abbreviation of the month. But that only works in English.
My software date and time stamps are always in the shortform of 190111-1227 (today) and any number that is larger is always a later time. Of course the long form is 2019/01/11 12:27 with the time in 24 hour format for the same reasons.
BTW - I understand the reasons for the U.S. format but that is only unambiguous if you spell it out as January 11, 2019 etc, not 1/11/19 which here in Oz and practically every other place in the world means the first of November.
Yeah I prefer hyphen separators for the date and 24hrs time with colon separator(s) too. Like yeti posted. That's what MySQL and other SQL normally use.
Using 24hrs format means that a simple ASCII sort will put date-times in order without needing special rules about interpreting AM or PM
evanh
Posts: 15,915
Comments
-Phil
BTW - I understand the reasons for the U.S. format but that is only unambiguous if you spell it out as January 11, 2019 etc, not 1/11/19 which here in Oz and practically every other place in the world means the first of November.
Using 24hrs format means that a simple ASCII sort will put date-times in order without needing special rules about interpreting AM or PM
+1 ... It is finally time to start using a sensible unambiguous time/date format.
This will be implemented soon.
-Phil