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

From David E. Wheeler
Subject Re: New to_timestamp implementation is pretty strict
Date
Msg-id F456DC32-06EB-4546-8683-7F0BE4E55B1F@kineticode.com
Whole thread Raw
In response to New to_timestamp implementation is pretty strict  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: New to_timestamp implementation is pretty strict  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: New to_timestamp implementation is pretty strict  ("Dave Page" <dpage@pgadmin.org>)
List pgsql-hackers
On Dec 1, 2008, at 1:08 PM, Heikki Linnakangas wrote:

> postgres=# SELECT to_timestamp('29-12-2005 01:02:3', 'DD-MM-YYYY  
> HH24:MI:SS'); -- doesn't work
> ERROR:  source string too short for "SS" formatting field
> DETAIL:  Field requires 2 characters, but only 1 remain.
> HINT:  If your source string is not fixed-width, try using the "FM"  
> modifier.
>
> 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.

My $0.02.

Best,

David


pgsql-hackers by date:

Previous
From: "Robert Haas"
Date:
Subject: Re: Simple postgresql.conf wizard
Next
From: Magnus Hagander
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Add support for matching wildcard server certificates to the new