[
https://issues.apache.org/jira/browse/DERBY-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407008#comment-15407008
]
Danoja Dias commented on DERBY-853:
-----------------------------------
I think, we can resolve this issue.
> ResultSetMetaData.getScale returns inconsistent values for DOUBLE type.
> -----------------------------------------------------------------------
>
> Key: DERBY-853
> URL: https://issues.apache.org/jira/browse/DERBY-853
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.2.1.6
> Reporter: Daniel John Debrunner
> Assignee: Danoja Dias
> Priority: Trivial
> Labels: derby_triage10_5_2
> Attachments: BryanPossibleIdea.diff, Derby-853.diff,
> Derby-853_2.diff, Derby-853_3.diff, Derby853.java
>
>
> If a DOUBLE column is returned in the result set then getScale() returns 0.
> If a DOUBLE expression is returned and the expression is the result of a
> DOUBLE combined with a DECIMAL then it seems the scale from the decimal
> sometimes affects the result set metadata.
> E.g. DECIMAL(10,2) - DOUBLE returns a DOUBLE with getScale() returning 2.
> See the test output for jdbcapi/metadata.java
> double -- precision: 15 scale: 0 display size: 22 type name: DOUBLE
> double precision - dec(10,2) -- precision: 15 scale: 0 display size: 22 type
> name: DOUBLE
> dec(10,2) - double precision -- precision: 15 scale: 2 display size: 22 type
> name: DOUBLE
> First line is a DOUBLE column, second is DOUBLE - DECIMAL, third is DECIMAL -
> DOUBLE
> I assume the scale should always be zero for a DOUBLE, as it holds no
> meaning, but I can't see any proof of that in JDBC spec, javadoc or tutorial
> book.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
