Tom Lane wrote:
> Bruce Momjian <[email protected]> writes:
> > The problem is that the 2-digit year check is for <=2 digits, not
> > exactly two digits:
> > ...
> > This leads to some unexpected outputs:
>
> > test=> select '1-1-0'::date;
> > date
> > ------------
> > 2000-01-01
>
> We've interpreted that like that since 7.4, without complaints; and
> I think it was an intentional change then (since 7.3 doesn't accept it).
> I do not recommend changing it.
OK, the release note text will be:
Reject year '0 BC' and years '000' and '0000' (Tom)
Previously these were interpreted as 1 BC.
--
Bruce Momjian <[email protected]> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
-
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
