Skip site navigation (1) Skip section navigation (2)

Re: Default numeric scale of zero in JDBC?

From: Todd Shoemaker <jtshoe11(at)yahoo(dot)com>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Default numeric scale of zero in JDBC?
Date: 2007-01-18 17:05:51
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbc

I downloaded the jdbc source and noted that if I specified a default scale of 4 in AbstractJdbc2ResultSetMetadata.getScale() (if the column is numeric and the scale is -1), I received the desired results.  I further updated the code to provide a private DEFAULT_NUMERIC_PRECISION that defaults to 4, which can be overridden with the System property org.postgresql.jdbc2.DEFAULT_NUMERIC_SCALE.  I built this and tested it within Squirrel SQL and it works properly, and the system property is working to override this default.  Would this be an update that the jdbc driver developers would be interested in?

I suppose my other question is, what do other JDBC drivers default this to?  Also, does this imply that others do not use non-integer arithmetic with sql through JDBC?


----- Original Message ----
From: Todd Shoemaker <jtshoe11(at)yahoo(dot)com>
To: pgsql-jdbc(at)postgresql(dot)org
Sent: Thursday, January 18, 2007 8:05:42 AM
Subject: [JDBC] Default numeric scale of zero in JDBC?


I have discovered that the jdbc driver apparently uses a default scale of zero decimal places for SQL numeric operators, including the sum() aggregate operator.  For example, this query:

select (1.5 + 2);

This returns 4 from jdbc, but it returns 3.5 when run from within PGAdmin.  The only way I can coerce the value to return decimal places is to explicity cast the value to a numeric with scale:

select cast(1.5 + 2 as numeric(10,2)) as value

This returns 3.5.  

Also, queries like "select sum(value) from table" returns a rounded value, even though the column 'value' is numeric(16,2).  Is there a magic vmparam or setting to default the precision at the jdbc driver level?  I am trying to run a large existing system on PostgreSQL and it is not feasible to hunt down all numeric operations in thousands of classes to explicitly cast them.   Have others have encountered this issue?



---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings


pgsql-jdbc by date

Next:From: Guillaume SmetDate: 2007-01-18 17:42:21
Subject: Re: Memory leaks using refcursors
Previous:From: Guillaume SmetDate: 2007-01-18 14:46:26
Subject: Re: Memory leaks using refcursors

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group