Re: timestamptz parsing bug?
От | Tom Lane |
---|---|
Тема | Re: timestamptz parsing bug? |
Дата | |
Msg-id | 10516.1314646202@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: timestamptz parsing bug? (Dean Rasheed <dean.a.rasheed@gmail.com>) |
Ответы |
Re: timestamptz parsing bug?
|
Список | pgsql-hackers |
Dean Rasheed <dean.a.rasheed@gmail.com> writes: > On 29 August 2011 15:40, Andrew Dunstan <andrew@dunslane.net> wrote: >> Why do we parse this as a correct timestamptz literal: >> 2011-08-29T09:11:14.123 CDT >> but not this: >> 2011-08-29T09:11:14.123 America/Chicago > For this input string the "T" is recognised as the start of an ISO > time, and the ptype variable is set to DTK_TIME. The next field is a > DTK_TIME, however, when it is handled it doesn't reset the ptype > variable. > 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? regards, tom lane
В списке pgsql-hackers по дате отправления: