From: | Kris Jurka <books(at)ejurka(dot)com> |
---|---|
To: | Jonathan Purvis <jon(at)reeltwo(dot)com> |
Cc: | <pgsql-bugs(at)postgresql(dot)org>, <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: JDBC driver doesn't handle NaN values |
Date: | 2004-01-09 09:30:12 |
Message-ID: | Pine.LNX.4.33.0401090418040.6759-200000@leary.csoft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-jdbc |
On Fri, 9 Jan 2004, Jonathan Purvis wrote:
> The JDBC driver that ships with PostgreSQL 7.4.1 doesn't insert floats
> of value NaN. As it uses Float.toString(x) to convert the value for
> insertion into the database, it tries to insert NaN instead of 'NaN' and
> gets the error "Attribute 'nan' not found". The same bug occurs for
> doubles and will probably occur for infinite values as well (i haven't
> tested it). This bug also exists in 7.2.4 and in the 7.2.1 version
> currently in Debian stable.
As you noted this is a problem with positive and negative infinity, but
there are some more problems as evidenced by the attached test case.
Double.MIN_VALUE will cause underflow.
Double.MAX_VALUE goes in alright, but comes out as POSITIVE_INFINITY
when trying Float.MAX_VALUE and MIN_VALUE on a real or float4 field they
overflow and underflow respectively.
Kris Jurka
Attachment | Content-Type | Size |
---|---|---|
Range.java | text/plain | 1.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Martin Holz | 2004-01-09 11:12:39 | Re: jdbc1.AbstractJdbc1Statement.setBinaryStream bug and |
Previous Message | Kris Jurka | 2004-01-09 08:46:04 | Re: jdbc1.AbstractJdbc1Statement.setBinaryStream bug and |
From | Date | Subject | |
---|---|---|---|
Next Message | Xavier Bugaud | 2004-01-09 09:53:04 | RE : Nmber of rows in a ResultSet |
Previous Message | Antonio Gallardo | 2004-01-09 09:17:53 | Re: [BUG] - Invalid UNICODE character sequence found |