From: | Troels Arvin <troels(at)arvin(dot)dk> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Non-standard TIMESTAMP WITH TIME ZONE literal handling |
Date: | 2003-08-07 11:04:37 |
Message-ID: | pan.2003.08.07.11.04.37.288286@arvin.dk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hello,
In Jim Melton and Alan Simon's "SQL:1999 - Understanding Relational
Language Components" (ISBN 1-55860-456-1), they write that the following
is to be interpreted as a TIMESTAMP WITH TIME ZONE value:
TIMESTAMP '2003-07-29 13:19:30.5+02:00'
PostgreSQL interprets the above as a TIMESTAMP WITHOUT TIME ZONE value of
'2003-07-29 13:19:30.5', i.e. it simply discards the '+02:00' part and
fails to interpret it as being of TIMESTAMP WITH TIME ZONE type.
Unless Melton+Simon are wrong, PostgreSQL is not completely following
SQL:1999 regarding TIMESTAMP-like literal parsing.
Furthermore, as Oracle behaves as Melton+Simon describes, subtle, but
potentially nasty portability problems can be imagined, hurting people
porting to/from Oracle.
--
Greetings from Troels Arvin, Copenhagen, Denmark
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-08-07 14:06:35 | Re: range query with timestamp returns different result with index than without (7.3.3) |
Previous Message | Christian van der Leeden | 2003-08-07 11:01:29 | Follow up: range query with timestamp returns different result with index than without (7.3.3) |