Re: mm/dd/yyyy format question
- From: "Cor Ligthert [MVP]" <notmyfirstname@xxxxxxxxx>
- Date: Wed, 21 Dec 2005 18:54:33 +0100
Joergen,
>
> The original question stated
> "what is the logical way to configure server, sql server or program so
> it always deals with date as mm/dd/yyyy format".
>
The SQL server nor a Net program do deal with a string format. Thet deal
with different ticks.
SQL server has ticks from 1000/3 millisecond starting at 1-1-1753 (for the
DateTime)
Net deals with ticks from a unit of hundred nanosecond starting at 1-1-1
> And I also said that I recommended the ISO approach when
> "passing date information as a string" (I use it myself and have
> never looked back).
>
I did as well however Net has better methods. By using direct the internal
DateTime and only use the string when it is needed to show it on screen or
get it from the sceen.
> I know that .Net takes care of all this provided that one goes
> through the proper objects.
>
> ISO 8601 specific to Asian countries? This is the first time I
> have heard that. Can you provide me with some links to some
> more information?
That is not so strange as you think that they don't use European languages.
The former communist countries have used it a while, however that is as well
gone again. I think that the Britans will drive earlier on the right lane
than ISO8601 is used in Europe. China started the Georgian calendar late in
1949 and Turkey in 1928. Most Islamic countries (not all see Turkey) have of
course there own calendar (Isreal as well an hebrewic). Therefore the main
ISO8601 countries are India and China. From other Asian countries I am not
sure what they use.
Searching for Calendar and ISO8601 in Google gives you a bunch of
information. So wants the state of Nevada only use ISO8601 in official
websites.
>As the article in the Microsoft link stated,
> the ISO format is unambiguous to SQL Server and is recommended
> for that reason, regardless of the locale settings or country.
The article is clear for me from a probably SQL part of Microsoft, not from
the Net or the OS part. How would you look to it if it was writen by
Navision/Microsoft.
> I only mentioned the ISO format because other posters started
> talking about mm-dd-yyyy and dd-mm-yyyy.
That I understood, however those dates have given often misunderstandings,
while it is so fine done in Net.
> If the original question had been about what .Net classes/objects to
> use in order to pass date information correctly to and from SQL
> Server, I suppose we would have had an entirely different
> discussion.
>
The way as Armin wrote it was in my opinon clear for the question. That was
why I did not add anything beside the warning to it, while I mostly do that
in DateTime questions.
(In my opinion is it a pity that the VBNet IDE shows all dateTimes in USA
format, whatever it internal is. C# shows it in the culture format from the
system, my favorite would be as it was showed in ISO8601 in all IDE's,
however that is noted as point for the future)
I hope that you now understand why I gave a reply on your message.
Cor
.
- Follow-Ups:
- Re: mm/dd/yyyy format question
- From: Joergen Bech
- Re: mm/dd/yyyy format question
- From: adh
- Re: mm/dd/yyyy format question
- References:
- Re: mm/dd/yyyy format question
- From: Joergen Bech
- Re: mm/dd/yyyy format question
- From: Cor Ligthert [MVP]
- Re: mm/dd/yyyy format question
- From: Joergen Bech
- Re: mm/dd/yyyy format question
- Prev by Date: Decimal comma / point problem in sql
- Next by Date: How do I move a project into another folder?
- Previous by thread: Re: mm/dd/yyyy format question
- Next by thread: Re: mm/dd/yyyy format question
- Index(es):
Relevant Pages
|
