Skip site navigation (1) Skip section navigation (2)

Re: BUG #1630: Wrong conversion in to_date() function. See example.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Fuhr <mike(at)fuhr(dot)org>
Cc: Ariel E(dot) Carná/Elizabeth Sosa <acarna(at)tarifar(dot)com>,pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1630: Wrong conversion in to_date() function. See example.
Date: 2005-04-27 14:53:52
Message-ID: 22259.1114613632@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Michael Fuhr <mike(at)fuhr(dot)org> writes:
> If anything I'd expect 2005-02-32 to be rejected as invalid, but I
> don't know the history or rationale behind to_date's behavior.

It is rejected by the standard date input converter:

regression=# select '2005-02-32'::date;
ERROR:  date/time field value out of range: "2005-02-32"
HINT:  Perhaps you need a different "datestyle" setting.

However we consider that to_date() exists to be Oracle compatible,
and so I would regard this as a bug if and only if Oracle does
something different with the same input.  Anyone know?

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2005-04-27 14:57:42
Subject: Re: BUG #1629: subquery IN returns incorrect results
Previous:From: Juan Miguel ParedesDate: 2005-04-27 14:50:23
Subject: Re: BUG #1630: Wrong conversion in to_date() function. See example.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group