Re: why setFloat() changed to Oid.FLOAT8?

On Fri, 3 Feb 2006, Trevor Baker wrote:

> 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?

This change was made to pass Sun's JDBC test suite.  Their test suite
requires the full precision of Float.MAX_VALUE to Float.MIN_VALUE to be
support for setFloat which requires pg's double type on the server side.

Kris Jurka