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

From: Kris Jurka <books(at)ejurka(dot)com>
To: Trevor Baker <amoebaworks(at)yahoo(dot)ca>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: why setFloat() changed to Oid.FLOAT8?
Date: 2006-02-03 19:18:47
Message-ID: Pine.BSO.4.61.0602031417100.9876@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

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

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Kris Jurka 2006-02-03 21:12:42 Re: escapeQuotes causes faults in DatabaseMataData
Previous Message Trevor Baker 2006-02-03 18:56:23 why setFloat() changed to Oid.FLOAT8?