Re: New to_timestamp implementation is pretty strict - Mailing list pgsql-hackers

From Tom Lane
Subject Re: New to_timestamp implementation is pretty strict
Date
Msg-id 17683.1228143141@sss.pgh.pa.us
Whole thread Raw
In response to Re: New to_timestamp implementation is pretty strict  ("David E. Wheeler" <david@kineticode.com>)
Responses Re: New to_timestamp implementation is pretty strict  ("David E. Wheeler" <david@kineticode.com>)
List pgsql-hackers
"David E. Wheeler" <david@kineticode.com> writes:
> On Dec 1, 2008, at 1:08 PM, Heikki Linnakangas wrote:
>> I think the end of string should be treated like a field separator,  
>> colon in this example, and we should accept both of the above.  
>> Opinions?

> I'm generally in favor of being generous in the input one can accept,  
> but in this case it seems ambiguous to me. Is that supposed to be :30  
> or :03? There's no way to tell.

But notice that we are allowing a single digit for the hour and minute
fields.  It's inconsistent that the last field works differently.
(And it is that it's the last field, not that it's SS --- try minutes
as the last field.)
        regards, tom lane


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Add support for matching wildcard server certificates to the new
Next
From: "Dave Page"
Date:
Subject: Re: New to_timestamp implementation is pretty strict