From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Datetime input-parsing shortcoming |
Date: | 1999-02-09 15:06:49 |
Message-ID: | 36C04F09.8B97E2B1@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Seen with current sources and with 6.4.2:
> When datestyle = 'Postgres,European', the datetime parser will accept
> dates written in either US or Euro order:
> But when datestyle = 'Postgres,US' it won't:
> regression=> select 'Wed 06 Jan 16:10:00 1999 EST'::datetime;
> ERROR: Bad datetime external representation
> A bug, no??
Si, though I would prefer to think of it as a "feature omission" since
it would have accepted a date sometimes (if the day of month was greater
than 12) :)
postgres=> show DateStyle;
NOTICE: DateStyle is Postgres with US (NonEuropean) conventions
postgres=> select 'Wed 06 Jan 16:10:00 1999 EST'::datetime;
----------------------------
Wed Jan 06 21:10:00 1999 GMT
(1 row)
Will apply to the development tree soon...
- Tom
Attachment | Content-Type | Size |
---|---|---|
dt.c.patch | text/plain | 2.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Williams | 1999-02-09 15:14:30 | Error dropping indexes |
Previous Message | Dan Gowin | 1999-02-09 14:59:16 | RE: [HACKERS] Timestamp fileds into index |