From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
---|---|
To: | Peter Haworth <pmh(at)edison(dot)ioppublishing(dot)com> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: this date format thing. |
Date: | 2003-04-03 17:39:13 |
Message-ID: | Pine.LNX.4.33.0304031038410.19813-100000@css120.ihs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 3 Apr 2003, Peter Haworth wrote:
> On Wed, 2 Apr 2003 13:23:45 -0700 (MST), scott.marlowe wrote:
> > While situations where 04-02 would get put in when the user meant 02-04,
> > at least enough of the 02-13 cases would throw an error that the user
> > would know they had been doing something wrong along the way and would
> > hopefully go back and look at their data.
>
> You wish.
>
> jnlstats=> select version();
> version
> -------------------------------------------------------------
> PostgreSQL 7.3.2 on i686-pc-linux-gnu, compiled by GCC 2.96
> (1 row)
>
> jnlstats=> set datestyle='ISO';
> SET
> jnlstats=> select '2001-12-31'::date;
> date
> ------------
> 2001-12-31
> (1 row)
>
> jnlstats=> select '2001-31-12'::date;
> date
> ------------
> 2001-12-31
> (1 row)
>
> jnlstats=> select to_date('2001-31-12','yyyy-mm-dd');
> to_date
> ------------
> 2003-07-14
> (1 row)
No, I was saying that if we fixed the parser that would happen. I know
it's horribly broken right now. Who hired Monty to work on our date
parsing routine anyway? :-)
From | Date | Subject | |
---|---|---|---|
Next Message | scott.marlowe | 2003-04-03 17:51:49 | Re: 'DROP INDEX' kills stored rpocedures |
Previous Message | Dennis Gearon | 2003-04-03 17:35:57 | Re: Rules, Triggers something more challenging |