On Tue, Apr 26, 2005 at 11:48:12PM +0100, Ariel E. Carná/Elizabeth Sosa wrote:
What bug are you reporting? These are the same date displayed in
different formats -- are you familiar with the DateStyle setting?

http://www.postgresql.org/docs/7.3/i...ATETIME-OUTPUT
http://www.postgresql.org/docs/7.4/i...ATETIME-OUTPUT

test=> SELECT version();
version
---------------------------------------------------------------------------
PostgreSQL 7.4.7 on sparc-sun-solaris2.9, compiled by GCC gcc (GCC) 3.4.2
(1 row)

test=> SET DateStyle TO 'ISO,MDY';
SET
test=> SELECT to_date('2005-02-32', 'YYYY-MM-DD');
to_date
------------
2005-03-04
(1 row)

test=> SET DateStyle TO 'Postgres,DMY';
SET
test=> SELECT to_date('2005-02-32', 'YYYY-MM-DD');
to_date
------------
04-03-2005
(1 row)

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.

--
Michael Fuhr
http://www.fuhr.org/~mfuhr/

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

"Ariel E. Carná/Elizabeth Sosa" <acarna (AT) tarifar (DOT) com> writes:
I'm not convinced that's a bug --- most implementations of the Unix
mktime function will handle out-of-range day numbers like that.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

------=_Part_1763_32557864.1114613423403
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Even javascript handles those dates the same way...

On 4/27/05, Tom Lane <tgl (AT) sss (DOT) pgh.pa.us> wrote:=20
------=_Part_1763_32557864.1114613423403
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<div>Even javascript handles those dates the same way...</div>
<div><br>&nbsp;</div>
<div><span class=3D"gmail_quote">On 4/27/05, <b class=3D"gmail_sendername">=
Tom Lane</b> &lt;<a href=3D"mailto:tgl (AT) sss (DOT) pgh.pa.us">tgl (AT) sss (DOT) pgh.pa.us</a>=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">&quot;Ariel E. Carn=C3=A1/Elizab=
eth Sosa&quot; &lt;<a href=3D"mailto:acarna (AT) tarifar (DOT) com">acarna (AT) tarifar (DOT) com=
</a>&gt; writes:
<br>&gt; PROD=3D# select to_date('2005-02-32', 'YYYY-MM-DD');<br>&gt;&nbsp;=
&nbsp; to_date<br>&gt; ------------<br>&gt;&nbsp;&nbsp;2005-03-04<br>&gt; (=
1 row)<br><br>I'm not convinced that's a bug --- most implementations of th=
e Unix<br>mktime function will handle out-of-range day numbers like that.
<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb sp;&nbsp;&nbsp; regards, =
tom lane<br><br>---------------------------(end of broadcast)--------------=
-------------<br>TIP 5: Have you checked our extensive FAQ?<br><br>&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs p;&nbsp;&nbsp;&nbsp;&nbsp=
;<a href=3D"http://www.postgresql.org/docs/faq">
http://www.postgresql.org/docs/faq</a><br></blockquote></div><br>
------=_Part_1763_32557864.1114613423403--

Michael Fuhr <mike (AT) fuhr (DOT) org> writes:
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

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Here is the output I get from Oracle:
================================================== ===

Connected to:
Oracle8 Enterprise Edition Release 8.0.6.3.0 -
Production

SELECT to_date('2005-02-27', 'YYYY-MM-DD') from dual
TO_DATE('2005-02-27','YYYY-MM-
------------------------------
2/27/2005
1 row selected

SELECT to_date('2005-02-29', 'YYYY-MM-DD') from dual
ORA-01839: date not valid for month specified

SELECT to_date('2005-02-32', 'YYYY-MM-DD') from dual;
ORA-01847: day of month must be between 1 and last day
of month

===========================================

Regards,

Shelby Cain

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly

With Oracle (at least since 6.x version) this conversion is wrong.


Atentamente ,=20

Ariel Carn=E1




-----Mensaje original-----
De: Tom Lane [mailto:tgl (AT) sss (DOT) pgh.pa.us]=20
Enviado el: Mi=E9rcoles, 27 de Abril de 2005 11:54 a.m.
Para: Michael Fuhr
CC: Ariel E. Carn=C3=A1/Elizabeth Sosa; pgsql-bugs (AT) postgresql (DOT) org
Asunto: Re: [BUGS] BUG #1630: Wrong conversion in to_date() function. See
example.=20

Michael Fuhr <mike (AT) fuhr (DOT) org> writes:
It is rejected by the standard date input converter:

regression=3D# 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


---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings