| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
| Cc: | 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-18 21:53:44 |
| Message-ID: | 4590.1055973224@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:
> On Wed, 18 Jun 2003, Tom Lane wrote:
>> I do now seem to recall an agreement that a GUC switch to disable
>> date-interpretation guessing would be okay, though.
> I'm pretty sure it was the other way around, make strict locale / date
> checking the standard and a GUC to turn it off for folks who really want
> to use a broken database. :-)
This is definitely a case where what is "broken" is in the eye of the
beholder. If the current behavior is broken, why have we had so few
complaints about it? It's been like that for quite a few years now.
I think that on grounds of backwards compatibility alone, we should
leave the out-of-the-box default behavior as it is.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Travis Hume | 2003-06-18 22:01:04 | Re: can't "grant all on database..." |
| Previous Message | Stephan Szabo | 2003-06-18 21:49:51 | Re: can't "grant all on database..." |