From: | Trevor Baker <amoebaworks(at)yahoo(dot)ca> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | why setFloat() changed to Oid.FLOAT8? |
Date: | 2006-02-03 18:56:23 |
Message-ID: | 20060203185624.76203.qmail@web54406.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Hi,
I'm thinking of upgrading from 8.0 to 8.1, but I'm
wondering why the change in
AbstractJdbc2Statement.setFloat() (and elsewhere in
the class) of floats now being Oid.FLOAT8 instead of
Ois.FLOAT4?
In 8.0, I have a few functions that take a REAL as
input, and I use setFloat (the 4-byte float equivalent
in java) to pass the values. But in 8.1, using
setFloat() now looks for functions that take DOUBLE
PRECISION because the change in mapping.
I know I can change my functions, tables and java
methods to DOUBLE PRECISION and setDouble() to use
8-byte floats to avoid this issue, but again just
wondering what's up with the 4-byte float support.
thanks,
Trevor Baker
__________________________________________________________
Find your next car at http://autos.yahoo.ca
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2006-02-03 19:18:47 | Re: why setFloat() changed to Oid.FLOAT8? |
Previous Message | Paolo Predonzani | 2006-02-03 16:54:41 | escapeQuotes causes faults in DatabaseMataData |