db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5546) ResultSet#updateBigDecimal on a REAL column does not do underflow checking
Date Tue, 05 Feb 2013 03:34:13 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13570917#comment-13570917

Dag H. Wanvik commented on DERBY-5546:

Talked to Lance. We should follow the advice in the JDBC specification on this [1], when writing
to a data source, throw DataTruncation if information is lost/truncated. On reading from a
data source, report (not throw) DataTruncation (a SQLWarning subclass). In this case, since
we are updating a column, we should throw.

[1] JDBC 4.1 specification section 8.3 DataTruncation [http://download.oracle.com/otndocs/jcp/jdbc-4_1-mrel-spec/index.html]

> ResultSet#updateBigDecimal on a REAL column does not do underflow checking
> --------------------------------------------------------------------------
>                 Key: DERBY-5546
>                 URL: https://issues.apache.org/jira/browse/DERBY-5546
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions:
>            Reporter: Dag H. Wanvik
>            Assignee: Dag H. Wanvik
>            Priority: Minor
>              Labels: derby_triage10_9
>         Attachments: derby-5546.diff, derby-5546.stat, MissingUnderflowCheck.java
> In contrast, ResultSet#updateBigDecimal on a FLOAT or DOUBLE column gives the expected
error on underflow. Cf. the attached repro program MissingUnderflowCheck.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message