| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <cmarin(at)dims(dot)com>, "Pgsql-General-post (E-mail)" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: A creepy story about dates. How to prevent it? |
| Date: | 2003-06-19 13:52:26 |
| Message-ID: | Pine.LNX.4.44.0306190024150.2501-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
scott.marlowe writes:
> That reminds me, did we get the date parsing fixed so that you can't
> insert 22/03/2003 into a european database (or conversely, 03/22/2003 into
> a US database) ? I.e the problem where the date parser assumed you meant
> it the other way...
I vaguely recall that we wanted to provide some kind of configuration
option to make the date format checking more strict. If I'm mistaken, I
would certainly be in favor of it now. But exactly how strict it ought to
be is up for discussion.
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2003-06-19 13:53:03 | Re: why are my SELECTs in transaction? |
| Previous Message | Peter Haworth | 2003-06-19 13:46:31 | Re: A creepy story about dates. How to prevent it? |