Re: Validation in to_date()

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Validation in to_date()
Date: 2013-01-14 20:14:41
Message-ID: 28727.1358194481@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com> writes:
> 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.

This looks like a good idea, will commit.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Smith 2013-01-14 20:37:40 Re: Timing events WIP v1
Previous Message David Johnston 2013-01-14 20:09:59 Re: count(*) of zero rows returns 1