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

From: Frank Miles <fpm(at)u(dot)washington(dot)edu>
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 14:40:32
Message-ID: Pine.A41.4.44.0306190736380.11078-100000@homer17.u.washington.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, 19 Jun 2003, 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)

If the application always passes the date to Postgres with the three-letter
month name where appropriate, and use the 4-digit year, it should be
comparatively bulletproof. At least, bulletproof in its interpretation --
the application can always garble things.

Not sure how this translates in different languages, though.

-frank

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message scott.marlowe 2003-06-19 14:51:14 Re: A creepy story about dates. How to prevent it?
Previous Message Paul Thomas 2003-06-19 14:36:39 Re: FW: Allowing user to connect to a database?