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

From: Dennis Gearon <gearond(at)cvc(dot)net>
To: Bruno Wolff III <bruno(at)wolff(dot)to>
Cc: Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net>, pgsql-general(at)postgresql(dot)org
Subject: Re: A creepy story about dates. How to prevent it?
Date: 2003-06-19 15:04:56
Message-ID: 3EF1D118.9070301@cvc.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I think he was thiniing about making the **IN** and out of the date functions to be ANSI only.

Bruno Wolff III wrote:

> On Thu, Jun 19, 2003 at 02:43:12 -0500,
> Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> wrote:
>
>>OTOH, Andrew Snow's method (alway use ANSI standard YYYY-MM-DD)
>>is guaranteed to work. Have your app convert to that format before
>>inserting, and then PostgreSQL is guaranteed to puke if there's
>>a problem.
>
>
> No it isn't. In 7.4:
> area=> select '2003-20-02'::date;
> date
> ------------
> 2003-02-20
> (1 row)
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Dennis Gearon 2003-06-19 15:07:53 Re: A creepy story about dates. How to prevent it?
Previous Message Dennis Gearon 2003-06-19 15:02:51 Re: Incremental backups, and backup history