From: | Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Validation in to_date() |
Date: | 2013-01-12 06:28:15 |
Message-ID: | CAP7QgmkvW6KeogQnNJHno1pyb7ifqQGShGoygN=fxsuv+36hdQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
to_date() doesn't check the date range, which results in unreadable
data like this.
foo=# create table t as select to_date('9999-12-10 BC', 'YYYY-MM-DD
BC')::timestamp;
SELECT 1
foo=# table t;
ERROR: timestamp out of range
Attached is to add IS_VALID_JULIAN() as we do like in date_in(). I
think to_date() should follow it because it is the entrance place to
check sanity.
Thanks,
--
Hitoshi Harada
Attachment | Content-Type | Size |
---|---|---|
to_date_check.patch | application/octet-stream | 614 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Boszormenyi Zoltan | 2013-01-12 07:42:54 | Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] |
Previous Message | Amit kapila | 2013-01-12 05:51:06 | Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] |