Non-standard TIMESTAMP WITH TIME ZONE literal handling - Mailing list pgsql-bugs

From Troels Arvin
Subject Non-standard TIMESTAMP WITH TIME ZONE literal handling
Date
Msg-id pan.2003.08.07.11.04.37.288286@arvin.dk
Whole thread Raw
Responses Re: Non-standard TIMESTAMP WITH TIME ZONE literal handling  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Non-standard TIMESTAMP WITH TIME ZONE literal handling  (Stephan Szabo <sszabo@megazone.bigpanda.com>)
List 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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Follow up: range query with timestamp returns different result with index than without (7.3.3)
Next
From: Tom Lane
Date:
Subject: Re: Non-standard TIMESTAMP WITH TIME ZONE literal handling