DataColumn.DataSetDateTime Property - What is it good for?

  • Thread starter Thread starter thomas
  • Start date Start date
T

thomas

Hello everybody,

When I saw this new DataColumn.DataSetDateTime property for the first time I
thought myself: wow, what a good idea! Perhaps ADO.Net seamlessly converts
UTC to local and vice versa, so I will be able to store dates as UTC but
display as local! All that just specifying DataSetDateTime property value.

But it does not seem to work quite that way. DataSet.Merge() operation
requires compatibility and does not perform any translations.
So, how is it supposed to be used? What is the hidden advantage?
Could someone share his/her experience? I already read docs, but the
description is rather scant.

Tomasz
 
Thomas,

Investigate how many timezones and how many Summertime (or in the USA
dayligh saving time) zones there are and by who the later ones are
regulated. Because especialy in the USA that seems not to be so obvious,
while in Europe there is AFAIK only a rule for the EU (on which some other
countries like Swiss confirm)..

Than you will understand why it is not so simple as you ask.

Cor
 
Hi Cor,

It is not so simple? You meant the UTC <-> local conversion? But the Windows
OS can do it? Right? I know, recently I had to write a T-SQL function which
does exactly that for US and it was an interesting task. Not to mention that
next year rule changes.

But, anyway, I understand what this property does not do.

Do you, by a chance, know what it does?

Tomasz
 
Cor,

Let me share another thought
Why do you think the complexity of this conversion matters at all? Why do
you think the average developer like myself should understand this
complexity? - like I said - I do.
..Net framework already implements DateTime.ToLocalTime() and
DateTime.ToUniversalTime() methods.
Do you think they are not reliable?

Tomasz
 
Hello everybody,

When I saw this new DataColumn.DataSetDateTime property for the first time I
thought myself: wow, what a good idea! Perhaps ADO.Net seamlessly converts
UTC to local and vice versa, so I will be able to store dates as UTC but
display as local! All that just specifying DataSetDateTime property value.

But it does not seem to work quite that way. DataSet.Merge() operation
requires compatibility and does not perform any translations.
So, how is it supposed to be used? What is the hidden advantage?
Could someone share his/her experience? I already read docs, but the
description is rather scant.

Tomasz
Click to expand...
Where are you seeing this property? I don't find it in the VS 2005 help index.
Are you using a beta or something?
Good luck with your project,

Otis Mukinfus
http://www.arltex.com
http://www.tomchilders.com
 
Thomas,

Let's try what I think I know about it.

As far as I know do they work from your system local time to UTC,
And than on my system from my UTC to my local time.

I am not sure if they work if you would change it on your UTC to my local
time.

Cor
 
Back
Top