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

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: nolan@celery.tssi.com
Cc: pmh@edison.ioppublishing.com (Peter Haworth), scott.marlowe@ihs.com (scott.marlowe), cmarin@dims.com, pgsql-general@postgresql.org (\"Pgsql-General-post E-mail\")
Date: 2003-06-19T18:09:00Z
Lists: pgsql-general
nolan@celery.tssi.com writes:
>>> Oracle's to_date function is not lax at all.
>> 
>> Then we need to fix ours.  Karel?

> To make it as strict as Oracle's?  I'm not entirely convinced that is a
> Good Thing.

But to_date is a different animal, because it's working from a format
string that tells it exactly which field is which.  So as far as I can
see, there's no ambiguity; rather, the present behavior seems like it's
accepting demonstrably bogus data.

			regards, tom lane