From: | amul sul <sul_amul(at)yahoo(dot)co(dot)in> |
---|---|
To: | Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Bug in to_timestamp(). |
Date: | 2016-06-23 07:41:26 |
Message-ID: | 884791796.213185.1466667686999.JavaMail.yahoo@mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Monday, 20 June 2016 8:53 PM, Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru> wrote:
>>On 13.06.2016 18:52, amul sul wrote:
>And it wont stop on some simple whitespace. By using to_timestamp you
>can get any output results by providing illegal input parameters values:
>postgres=# SELECT TO_TIMESTAMP('2016-06-13 99:99:99', 'YYYYMMDD
>HH24:MI:SS');
> to_timestamp
>------------------------
> 2016-01-06 14:40:39+03
>
> (1 row)
We do consume extra space from input string, but not if it is in format string, see below:
postgres=# SELECT TO_TIMESTAMP('2016-06-13 15:43:36', 'YYYY/MM/DD HH24:MI:SS');
to_timestamp
------------------------
2016-06-13 15:43:36-07
(1 row)
We should have same treatment for format string too.
Thoughts? Comments?
Regards,
Amul Sul
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2016-06-23 07:55:02 | PQconnectdbParams vs PQconninfoParse |
Previous Message | Masahiko Sawada | 2016-06-23 07:24:12 | Comment and function argument names are mismatched in bugmgr.c. |