| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: New to_timestamp implementation is pretty strict |
| Date: | 2008-12-01 15:26:07 |
| Message-ID: | 4934020F.3060901@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dave Page wrote:
> On Mon, Dec 1, 2008 at 3:02 PM, David E. Wheeler <david(at)kineticode(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2008-12-01 15:31:46 | Re: Re: [COMMITTERS] pgsql: Add support for matching wildcard server certificates to the new |
| Previous Message | David E. Wheeler | 2008-12-01 15:14:18 | Re: New to_timestamp implementation is pretty strict |