From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
---|---|
To: | Todd Shoemaker <jtshoe11(at)yahoo(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Default numeric scale of zero in JDBC? |
Date: | 2007-01-18 21:54:36 |
Message-ID: | 45AFEC9C.7080102@opencloud.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Todd Shoemaker wrote:
> Hello,
>
> 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?
Given that the reported metadata scale does not affect what the driver
does at all, and all the computation is done on the server side, I'd say
that any rounding that is happening is happening in whatever is using
the driver's metadata ("Squirrel SQL?")
-O
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2007-01-19 00:03:16 | Re: Memory leaks using refcursors |
Previous Message | Guillaume Smet | 2007-01-18 17:42:21 | Re: Memory leaks using refcursors |