Skip site navigation (1) Skip section navigation (2)

Re: timestamptz parsing bug?

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: timestamptz parsing bug?
Date: 2011-08-29 19:43:57
Message-ID: 4E5BEBFD.4090800@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackers

On 08/29/2011 03:35 PM, David E. Wheeler wrote:
> On Aug 29, 2011, at 12:30 PM, Tom Lane wrote:
>
>>> When it gets to the timezone "America/Chicago" at the end, this is
>>> handled in the DTK_DATE case, because of the "/". But because ptype is
>>> still set, it is expecting this to be an ISO time, so it errors out.
>> Do we actually *want* to support this?  The "T" is supposed to mean that
>> the string is strictly ISO-conformant, no?
> I didn't realize that appending a time zone was not conformant, but apparently it's not.
>
>    http://en.wikipedia.org/wiki/ISO_8601#Time_zone_designators
>
> Only appending a "Z" or an offset seems to be legal. Interesting.
>
>

In that case we shouldn't be accepting an abbreviation either.

cheers

andrew

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2011-08-29 20:29:39
Subject: Re: timestamptz parsing bug?
Previous:From: David E. WheelerDate: 2011-08-29 19:35:25
Subject: Re: timestamptz parsing bug?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group