Thank you Michael for your very thoughtful reply. I know that it takes
time and effort to answer at the level you did.
Michael Stassen Michael.Stassen-at-verizon.net |Lists| wrote:
You seem to have a fundamental misunderstanding of the TIMESTAMP type.
No timezone or DST information is stored
Peter Valdemar Mørch wrote:
From the lack of responses I take it that nobody disagrees that the
handling of the timestamp type is fundamentally broken in every version
of MySQL.
Silence does not necessarily indicate assent. You asked a complicated
question (when the U.S. list members were on
From the lack of responses I take it that nobody disagrees that the
handling of the timestamp type is fundamentally broken in every version
of MySQL.
I'll go ahead and file several bugs, and start changing our code to
avoid the timestamp type altogther. I'm quite surprised!
Peter
Peter
***
Claim
***
I seem to have discovered that MySQL cannot handle the hour where DST
becomes non-DST reliably (on Oct 31st in CET):
2am 3am
| problem |
| time|
