From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Magne Mæhre <Magne(dot)Mahre(at)sun(dot)com>, Trevor Talbot <quension(at)gmail(dot)com> |
Subject: | Re: Timezone database changes |
Date: | 2007-10-09 12:36:28 |
Message-ID: | 200710091436.29233.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Am Dienstag, 9. Oktober 2007 schrieb Magne Mæhre:
> SQL itself doesn't say anything how the data element should be stored,
> only how it should be operated upon. It do, however,say that a
> datetime/time WITH TIME ZONE represents the time in UTC (SQL 2003,
> §4.3). All operations on the element are defined as if it's an instance
> in time (in UTC).
There is, generally, a significant mismatch between the time zone handling
specified in SQL and practical requirements. More specifically, SQL only
supports time zones with fixed offsets and does not support daylight-saving
time rules at all.
Independent of what any specification might say, however, the currently
implemented behavior is clearly wrong in my mind and needs to be fixed.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
From | Date | Subject | |
---|---|---|---|
Next Message | Nikolay Samokhvalov | 2007-10-09 12:52:30 | Re: mal advice in FAQ 4.1. |
Previous Message | Pavel Stehule | 2007-10-09 12:28:24 | some points for FAQ |