From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> |
Cc: | Theodore Petrosky <tedpet5(at)yahoo(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: is this my date problem |
Date: | 2003-10-02 14:04:39 |
Message-ID: | 26742.1065103479@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> writes:
> The to_timestamp() do nothing with date/time and use internal
> tm2timestamp() routine only. I don't think that check all date/time
> ranges in to_timestamp() is good idea if it's already implemented at
> the another place in our code.
But it evidently *isn't* checked. As of CVS tip:
regression=# select to_timestamp('44 October 2003', 'DD FMMonth YYYY');
to_timestamp
------------------------
2003-11-13 00:00:00-05
(1 row)
The regular timestamp input converter certainly has the checks:
regression=# select '44 October 2003'::timestamp;
ERROR: invalid input syntax for type timestamp: "44 October 2003"
but evidently those checks are not in whatever code path to_timestamp
is calling.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Karel Zak | 2003-10-02 14:42:50 | Re: is this my date problem |
Previous Message | Theodore Petrosky | 2003-10-02 12:15:39 | Re: is this my date problem |