From: | Oliver Siegmar <o(dot)siegmar(at)vitrado(dot)de> |
---|---|
To: | Kris Jurka <books(at)ejurka(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Problems with infinity |
Date: | 2005-01-13 13:52:31 |
Message-ID: | 200501131452.31209.o.siegmar@vitrado.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Thursday 13 January 2005 14:42, Kris Jurka wrote:
> On Thu, 13 Jan 2005, Oliver Siegmar wrote:
> > Caused by: org.postgresql.util.PSQLException: Bad Timestamp Format at 0
> > in 9999-01-01
>
> This is indeed a bug in the 7.4 drivers.
Will you fix it? ;-)
> You may use getString() on the column and check for infinity yourself.
> Using setString(x, "Infinity") will work with the 7.4 drivers, but not
> 8.0. Perhaps we could make setObject(x, "Infinity", Types.TIMESTAMP)
> accomodate this though...
I'm using Hibernate for getting/setting data - I don't access the data
directly. Dropping infinity support, means I cannot work with Hibernate on
databases with infinite timestamps :-((
Couldn't you make it configurable (like 'convert_infinite_to_min_max = true')?
Cheers,
Oliver
--
- Technik -
www.vitrado.de
Fax: +49 (0)89 - 62 44 77 - 39
vitrado GmbH
Grillparzerstrasse 3
81675 München
______________________________________
Geschäftsführer: Thorsten Meier, Martin Plöckl
Amtsgericht München, HRB 13119
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2005-01-13 14:18:09 | Re: Problems with infinity |
Previous Message | Kris Jurka | 2005-01-13 13:42:07 | Re: Problems with infinity |