Re: JDBC CallableStatement bug on functions with return parameter - Mailing list pgsql-jdbc

From Kevin Grittner
Subject Re: JDBC CallableStatement bug on functions with return parameter
Date
Msg-id 4D4D37E5020000250003A45D@gw.wicourts.gov
Whole thread Raw
Responses Re: JDBC CallableStatement bug on functions with return parameter
List pgsql-jdbc
John LH  wrote:

> callStatement.registerOutParameter(1, java.sql.Types.FLOAT);

> callStatement.setObject(2, new Float(25.25));

PostgreSQL doesn't support using approximate data types (like Float)
for money.  Try compiling and running this to see why:

import java.math.BigDecimal;
public class ExactnessTest
{
    public static void main(String[] args)
    {
        double approximate;
        BigDecimal exact;

        // Set an approximation of a penny.
        approximate = 0.01;
        // Put the actual value into an exact class.
        exact = new BigDecimal(approximate);
        // Show the actual value assigned to the double.
        System.out.println(exact);
        // Create and show an exact decimal penny.
        exact = new BigDecimal("0.01");
        System.out.println(exact);
    }
}

Try using BigDecimal, which *is* capable of storing exact
representations of all decimal fractions.  Note that feeding an
approximate value, including an unquoted literal, to the BigDecimal
constructor will cause the BigDecimal value to be less precise than
you might expect.

-Kevin

pgsql-jdbc by date:

Previous
From: John LH
Date:
Subject: Re: JDBC CallableStatement bug on functions with return parameter
Next
From: John LH
Date:
Subject: Re: JDBC CallableStatement bug on functions with return parameter