| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
| 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 17:44:53 |
| Message-ID: | 2134.1056390293@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert J. Sanford, Jr. | 2003-06-23 17:58:34 | SELECT @@IDENTITY |
| Previous Message | scott.marlowe | 2003-06-23 17:39:35 | Re: [GENERAL] interesting PHP/MySQL thread |