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

From Andrew Dunstan
Subject Re: New to_timestamp implementation is pretty strict
Date
Msg-id 4934020F.3060901@dunslane.net
Whole thread Raw
In response to Re: New to_timestamp implementation is pretty strict  ("Dave Page" <dpage@pgadmin.org>)
Responses Re: New to_timestamp implementation is pretty strict  ("Greg Stark" <stark@enterprisedb.com>)
List pgsql-hackers

Dave Page wrote:
> On Mon, Dec 1, 2008 at 3:02 PM, David E. Wheeler <david@kineticode.com> wrote:
>
>   
>> it depends on how you look at it, I suppose. If you look at ":xy" as "x"
>> being the 10s position and "y" being the 1s position, it makes no sense.
>>     
>
> Suffice it to say, I don't look at it that way :-). I'd wager most
> people wouldn't either, but I have no data to back that up of course.
>
>
>   

Isn't the point that ambiguity is undesirable, as is inconsistency? So 
counts of people who see this one way or the other should be irrelevant.

Alvaro noted the use in the wild of formats like "%d:%d:%d" for times. 
IMNSHO we should not cater to such bad code.

cheers

andrew

cheers


pgsql-hackers by date:

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