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

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

nolan(at)celery(dot)tssi(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Pavel Stehule 2003-06-19 18:11:38 Re: How to process mail using pgSQL?
Previous Message Steve Crawford 2003-06-19 17:48:17 Re: Single Instance of Backend