From: | "Ariel Carna" <acarna(at)tarifar(dot)com> |
---|---|
To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "'Michael Fuhr'" <mike(at)fuhr(dot)org> |
Cc: | <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #1630: Wrong conversion in to_date() function. See example. |
Date: | 2005-04-27 15:06:13 |
Message-ID: | 20050427150126.B2BAE18F42@fox.tarifar.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
With Oracle (at least since 6.x version) this conversion is wrong.
Atentamente ,
Ariel Carná
-----Mensaje original-----
De: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Enviado el: Miércoles, 27 de Abril de 2005 11:54 a.m.
Para: Michael Fuhr
CC: Ariel E. Carná/Elizabeth Sosa; pgsql-bugs(at)postgresql(dot)org
Asunto: Re: [BUGS] BUG #1630: Wrong conversion in to_date() function. See
example.
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
From | Date | Subject | |
---|---|---|---|
Next Message | Sokolov Yura | 2005-04-27 15:07:22 | BUG 1614 and BUG 1616 : Inadequate GIST Behaviour |
Previous Message | Russell Smith | 2005-04-27 15:01:01 | Re: BUG #1629: subquery IN returns incorrect results |