| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, 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:16:48 |
| Message-ID: | Pine.LNX.4.44.0306232112360.2285-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane writes:
> 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.
That might even make the slightest sense if the supposedly wrong datestyle
would then stay switched. But the automatic switching only happens for a
certain subsets of inputs and only in that instance. So if a user did
really mean the opposite setting he will not be happy, and if the user did
not mean the opposite setting he will not be happy either. So no one is
happy.
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-06-23 19:22:20 | Re: A creepy story about dates. How to prevent it? |
| Previous Message | Carlos | 2003-06-23 19:16:28 | Eliminating start error message: "unary operator expected" |