Neil Conway <[EMAIL PROTECTED]> writes:
> When integer datetimes are in use, the legal range of the "date" type
> actually exceeds that of the "timestamp" type. However, the cast from
> date => timestamp fails to take this into account:
Fixed, but I didn't bother to back-patch it.
OK, moved to patches queue.
---
Neil Conway wrote:
> On Wed, 2007-16-05 at 11:46 -0400, Bruce Momjian wrote:
> > This has been saved for the 8.4 release
>
> No, this is a bug, and should be fixed in 8.3 and likely backporte
On Wed, 2007-16-05 at 11:46 -0400, Bruce Momjian wrote:
> This has been saved for the 8.4 release
No, this is a bug, and should be fixed in 8.3 and likely backported. I
haven't had a chance to get to it yet, though.
-Neil
---(end of broadcast)---
This has been saved for the 8.4 release:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
---
Neil Conway wrote:
> When integer datetimes are in use, the legal range of the "date" type
> actually exceeds that of
When integer datetimes are in use, the legal range of the "date" type
actually exceeds that of the "timestamp" type. However, the cast from
date => timestamp fails to take this into account:
postgres=# select '01-01-5874896'::date::timestamp;
timestamp
--
