Re: A creepy story about dates. How to prevent it?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Peter Haworth" <pmh(at)edison(dot)ioppublishing(dot)com>
Cc: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>, cmarin(at)dims(dot)com, "Pgsql-General-post (E-mail)" <pgsql-general(at)postgresql(dot)org>
Subject: Re: A creepy story about dates. How to prevent it?
Date: 2003-06-19 14:10:22
Message-ID: 8456.1056031822@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Peter Haworth" <pmh(at)edison(dot)ioppublishing(dot)com> writes:
> On Wed, 18 Jun 2003 15:09:44 -0600 (MDT), scott.marlowe wrote:
>> Why not accept a date of 04/44/2003 and just wrap it into May?

> Unbelievably, to_date() already does that in 7.3.3:

It's only "unbelievable" if Oracle doesn't do the same thing. to_date
and friends are Oracle compatibility functions and are intended to
slavishly imitate what Oracle does, warts and all (and there are
certainly plenty of warts there...)

Anyone care to run some tests to see how lax Oracle's to_date is?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Nigel J. Andrews 2003-06-19 14:11:31 Re: attisdropped, * expansion and tg_trigtuple
Previous Message scott.marlowe 2003-06-19 14:08:58 Re: A creepy story about dates. How to prevent it?