| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Trevor Talbot" <quension(at)gmail(dot)com>, Magne MÃ|hre <Magne(dot)Mahre(at)Sun(dot)COM> |
| Cc: | "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Timezone database changes |
| Date: | 2007-10-09 14:50:44 |
| Message-ID: | 470B4EF4.EE98.0025.0@wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>> On Tue, Oct 9, 2007 at 6:49 AM, in message
<470B6AD4(dot)6080502(at)sun(dot)com>, Magne
Mæhre <Magne(dot)Mahre(at)Sun(dot)COM> wrote:
>
> Interestingly, if you cast a TIMESTAMP WITH TIME ZONE to a character
> value, it should be converted with the _original_ time zone value
(SQL
> 2003, *5.8) _unless_ you specify "AT LOCAL".
A lot of the ANSI/ISO behavior is broken if TIMESTAMP WITH TIME ZONE
does
not include the time zone. One of the least standards compliant areas
of
PostgreSQL is the date/time arithmetic; but any attempt to implement
the
standard date math will fail until the time zone is part of the WITH
TIME
ZONE data types.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2007-10-09 15:04:39 | Re: Timezone database changes |
| Previous Message | Kevin Grittner | 2007-10-09 14:43:47 | Re: Timezone database changes |