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-6088) PreparedStatementTest42 lacks "fail" call when operation unexpectedly succeeds
Date Fri, 22 Feb 2013 03:58:12 GMT

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

Dag H. Wanvik commented on DERBY-6088:
--------------------------------------

Inserting it, sees the test fail for TINYINT. This type is present in the test's array ILLEGAL_JDBC_TYPES,
but not in the code used for checking: ConnectionChild#checkForSupportedDataType and on the
client, similarly in PreparedStatement#checkForSupportedDataType.

                
> PreparedStatementTest42 lacks "fail" call when operation unexpectedly succeeds
> ------------------------------------------------------------------------------
>
>                 Key: DERBY-6088
>                 URL: https://issues.apache.org/jira/browse/DERBY-6088
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Test
>    Affects Versions: 10.10.0.0
>            Reporter: Dag H. Wanvik
>
> Ca line 233, this construct lacks a "fail()":
>     // verify that certain SQLTypes are illegal
>     for ( int i = 0; i < ILLEGAL_JDBC_TYPES.length; i++ )
>     {
>         try {
>             insert.setObject( 1, null, ILLEGAL_JDBC_TYPES[ i ] );
>         }
>         catch (SQLException se)
>         {
>             assertSQLState( UNIMPLEMENTED_FEATURE, se );
>         }
>     }

--
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

Mime
View raw message