| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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 14:56:52 |
| Message-ID: | 7E82016B-4E21-4DED-943F-339A3FD3B02C@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Dec 1, 2008, at 3:52 PM, Tom Lane wrote:
>> 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.)
Oh, well yeah, it should be consistent. But I'm still not sure that :3
should be allowed. OTOH, who does that, anyway?
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2008-12-01 15:02:39 | Re: Re: [COMMITTERS] pgsql: Add support for matching wildcard server certificates to the new |
| Previous Message | Dave Page | 2008-12-01 14:55:12 | Re: New to_timestamp implementation is pretty strict |