Subscribe to this thread
Home - General / All posts - Date/time format in M9 and M8
vincent

1,919 post(s)
#29-Jul-20 16:45

Hi,

On my computer, the SQL Datetime format is not the same for M8 and M9. There are like this :

M8 : 2020-03-19 19:08:55

M9 : 03/19/2020 19:08:55

It looks like M8 is using the Regional Parameters of my computer and M9 is not.

Is there a way to change the format in M9 ?

Thank you.

tjhb

9,320 post(s)
#29-Jul-20 18:19

In short, no.

See http://www.georeference.org/forum/t143927.7#143928.

This creates an almost unavoidable trap for non-US users when importing date-time from CSV format, for example, among others.

Once data is correct within Manifold (and known to be in "correct" order, in en-US terms) it can be ~managed using DateTime... functions, to manage elements of the date-time type separately--and perhaps store them in separate fields, for safety.

It's not a great situation. In my opinion it makes Manifold's date-time data type unsafe to use for most of the world.

dale

558 post(s)
#30-Jul-20 00:35

Same as SA units. Kilometre and metre.

tjhb

9,320 post(s)
#30-Jul-20 01:14

Can you expand? Do you mean the SI vs US spelling?

dale

558 post(s)
#30-Jul-20 04:42

My apologies, yes I do. It's still commonplace to spell *metres so SI spelling, in my part of the world.

As far as my extremely cursory search of the manual goes, I have only US distances (feet, inches, chains, Tlalcuahuitl, etc) or US metric (*meters) as a choice.

tjhb

9,320 post(s)
#30-Jul-20 07:42

SI units are SI. US spelling of them is plain stupid. (Lives at stake.)

I wonder if we could ask Manifold to adopt international standards, except for the USA if absolutely necessary. (I am going to look up what Canada does.)

dale

558 post(s)
#30-Jul-20 11:06

Would a localisation file work?

Dimitri

6,104 post(s)
online
#30-Jul-20 11:53

No, as unit names (currently) are not localizable.

vincent

1,919 post(s)
#30-Jul-20 12:59

Canada : SI rules.

tonyw
595 post(s)
#30-Jul-20 17:14

(I am going to look up what Canada does.)

Hi Tim, I'm in Canada. It's a mash-up, sometimes of a very serious nature. in technical work we follow the SI spelling ("metre") for units. However because we are right next door to the USA and given their population is 10 times Canada's and there is major spill over the border of their newscasts, media, different people in Canada use both SI standard and US variants. Dates are probably the worst for ambiguity. Seeing 03-04-2020 is really ambiguous. So is that April 3, 2020? No most times the majority of Canadians mean March 4, 2020 substituting 03 for March.

That spills into data sets I see. If we are lucky and we have enough dates in a data set there will be a number larger than 12 in one of the positions in the date and from that we can figure out which system the author used, a number larger than 12 can only be "day" in that position. So 04-28-2020 and 28-04-2020 can only be April 28, 2020.

The federal government in Canada has jurisdiction over weights and measures and has official guidelines (but not that everyone follows the official guidelines) for dates writing either big to small 2020-04-03 (April 3, 2020) or small to big, 03-04-2020 for April 3, 2020. Either way is unambiguous, month is always in the middle. However I'd say the majority of Canadians put the day in the middle and we don't know what the author's preference when we acquire data. We can only examine the data looking for clues (a number larger than 12).

Time is another problem. I use the 24 hour clock in data, it's unambiguous. However you see a lot of data with 12 hour clocks and AM and PM. Worse is if the time is a text field being a mix of numbers and text. Argh.

Manifold User Community Use Agreement Copyright (C) 2007-2019 Manifold Software Limited. All rights reserved.