Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Message-Id: <200409092121.i89LLo5m032259@mail.asynchrony.com>
From: "Nate McKie" <nate.mckie@asolutions.com>
To: <derby-user@db.apache.org>
Subject: Inconsistencies in PreparedStatement.setFloat/setDouble
Date: Thu, 9 Sep 2004 16:24:44 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AcSWs2z9dot0e8f8QEmwCKp1AXcP5A==


We have found in using Cloudscape/Derby that there are inconsistencies in
the behavior of how floating-point numbers are saved to the database
depending on whether you use PreparedStatement.setFloat or
PreparedStatement.setDouble.  setDouble seems to work better.

These problems are predictable and repeatable, and we've written some Junit
tests to show what happens.  Here's a link to the base code for what we
wrote:

	http://demo0.asolutions.com/CloudscapeInsertionAnomalyTest.java

You can't run this code without the database schema and some helper classes,
but I can assure you that all of these tests pass.

Does anyone know what's going on here, or have any suggestions?  Do I need
to submit this information more formally to get the problem resolved?

Thanks,

Nate McKie
Asynchrony Solutions, Inc.
www.asolutions.com