From: | Chris Browne <cbbrowne(at)acm(dot)org> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #5747: TimeStamps too far into the future are invalid |
Date: | 2010-11-10 22:56:23 |
Message-ID: | 87tyjog548.fsf@cbbrowne.afilias-int.info |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) writes:
> https://issues.apache.org/jira/browse/JUDDI-374
There's an issue that JDBC doesn't cope very well with 'Infinity'
values, which is more or less the opposite of what's reported here. I
have been tending to put "don't allow +/-Infinity" constraints onto
timestamps to avoid that particular impedance mismatch.
Just ran a little test of this with...
PostgreSQL 8.3.3, last year's JDBC, and had no difficulties pushing in
the date "2100-01-01 00:00:00".
That suggests the problem to be elsewhere. (As, I expect, you would
expect!)
--
(format nil "~S(at)~S" "cbbrowne" "gmail.com")
Rules of the Evil Overlord #194. "I will make several ludicrously
erroneous maps to secret passages in my fortress and hire travellers
to entrust them to aged hermits." <http://www.eviloverlord.com/>
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2010-11-11 00:20:09 | Re: Recovery bug |
Previous Message | Tom Lane | 2010-11-10 18:57:27 | Re: BUG #5745: geometry bug? |