| From: | "Robert Haas" <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | "Greg Stark" <stark(at)enterprisedb(dot)com> |
| Cc: | "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Dave Page" <dpage(at)pgadmin(dot)org>, "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:46:49 |
| Message-ID: | 603c8f070812010746ufa66e15n8e7a8a09149c94e5@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Dec 1, 2008 at 10:33 AM, Greg Stark <stark(at)enterprisedb(dot)com> wrote:
> How would you parse an input format of just 'SS' ? is there something
> ambiguous about '3' ? I don't see anything "bad" about using %d to
> output an integer number of seconds.
+1.
It seems to me that it's pretty silly to say that we "know" that the 2
in "01:2:03" is intended to mean 02, but we are somehow confused about
whether the 3 in "01:02:3" is intended to mean 03 or 30. Sure, the
latter could be the result of a truncation, but if the user is
randomly truncating their strings, they're going to have problems with
a lot more than to_timestamp().
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2008-12-01 15:50:35 | Re: New to_timestamp implementation is pretty strict |
| Previous Message | Magnus Hagander | 2008-12-01 15:41:16 | Re: Re: [COMMITTERS] pgsql: Add support for matching wildcard server certificates to the new |