| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | "Dave Page" <dpage(at)pgadmin(dot)org> |
| 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 15:02:59 |
| Message-ID: | C28D0F97-787C-44C0-86CD-E26680EEC476@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Dec 1, 2008, at 3:55 PM, Dave Page 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.
>
> How is it ambiguous? The leading zero is technically redundant. A
> trailing on most certainly isn't.
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. If you look at it as an integer, it does.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2008-12-01 15:05:50 | Re: Re: [COMMITTERS] pgsql: Add support for matching wildcard server certificates to the new |
| Previous Message | Robert Haas | 2008-12-01 15:02:39 | Re: Re: [COMMITTERS] pgsql: Add support for matching wildcard server certificates to the new |