From: | "Mendola Gaetano" <mendola(at)bigfoot(dot)com> |
---|---|
To: | <pgsql-hackers(at)postgresql(dot)org> |
Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Subject: | Re: Date input changed in 7.4 ? |
Date: | 2003-08-26 15:53:25 |
Message-ID: | 000b01c36bea$2f584860$152aa8c0@GMENDOLA2 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> wrote:
> Mendola Gaetano wrote:
> > Hi all,
> > I noticed that some date are not anymore accepted:
> >
> >
> > Postgres 7.3.3:
> >
> > test=# select '18/03/71'::date;
> > date
> > ------------
> > 1971-03-18
> > (1 row)
> >
> >
> > Postgres 7.4beta1:
> >
> > test=# select '18/03/71'::date;
> > ERROR: invalid input syntax for date: "18/03/71"
> >
> >
> > is this the indendeed behaviour ?
>
> Yes, we now honor datestyle to determine how to deal with dates where
> the year is at the end. You can set your date style to 'euopean' or the
> new 'DMY' value to allow this.
>
> This highlights the fact I need to get the compatibility section written
> for the history file soon.
May I also suggest to change in date.c the 3 generic error:
"invalid input syntax for date: "
with more comprensive messages ?
Regards
Gaetano Mendola
From | Date | Subject | |
---|---|---|---|
Next Message | Mendola Gaetano | 2003-08-26 15:58:17 | Re: Date input changed in 7.4 ? |
Previous Message | Tom Lane | 2003-08-26 15:48:35 | Re: Date input changed in 7.4 ? |