From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "Thomas Kellerer *EXTERN*" <spam_eater(at)gmx(dot)net>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: to_date() and invalid dates |
Date: | 2014-01-20 14:29:27 |
Message-ID: | A737B7A37273E048B164557ADEF4A58B17C9140E@ntex2010i.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thomas Kellerer wrote:
> I asked this a while back already:
>
> select to_date('2013-02-31', 'yyyy-mm-dd');
>
> will not generate an error (unlike e.g. Oracle)
This is by design.
> However in the release notes of 9.2.3[1] it is mentioned that
>
> - Reject out-of-range dates in to_date() (Hitoshi Harada)
>
> I tried the above statement using 9.2.6 and 9.3.2 in both versions 2013-02-03 is returned instead of
> rejecting the input.
> The same is true if e.g. an invalid month is specified: to_date('2013-17-09', 'yyyy-mm-dd').
>
> Does this check need a configuration setting to be in effect?
This commit only rejects dates that are before 4713 BC and 5874898 AD,
which cannot be printed reasonably.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Michael P. Soulier | 2014-01-20 14:33:57 | incrementing without violating a constraint |
Previous Message | Thomas Kellerer | 2014-01-20 13:44:34 | to_date() and invalid dates |