From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Jean-Luc Lachance <jllachan(at)nsd(dot)ca>, Frank Miles <fpm(at)u(dot)washington(dot)edu>, Bruno Wolff III <bruno(at)wolff(dot)to>, 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-23 19:11:12 |
Message-ID: | Pine.LNX.4.33.0306231310110.24557-100000@css120.ihs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 23 Jun 2003, Tom Lane wrote:
> "scott.marlowe" <scott(dot)marlowe(at)ihs(dot)com> writes:
> > The one thing that should absolutely be turned off is day/month swapping
> > on dates of the form: 2003-02-22.
>
> Agreed on that. YYYY-DD-MM isn't used in the real world AFAIK, and it's
> reasonable to treat it as an error.
>
> > I've seen little actual defense of the current behaviour,
>
> Other than me, I think you mean. dd/mm/yyyy and mm/dd/yyyy are
> inherently ambiguous in the real world, and when you can clearly
> determine what the intended meaning is, I think it's more reasonable
> to assume the datestyle isn't set correctly than to reject the data.
I thought the locale set that kind of behaviour didn't it? If so, then
it's better to fail loudly then quietly accept bad data. But if the
locale doesn't define such a thing, or it can't be set in postgresql.conf,
the it's best to just avoid that date style altogether.
From | Date | Subject | |
---|---|---|---|
Next Message | Carlos | 2003-06-23 19:16:28 | Eliminating start error message: "unary operator expected" |
Previous Message | Franco Bruno Borghesi | 2003-06-23 18:54:05 | Re: SELECT @@IDENTITY |