[DERBY-6088] PreparedStatementTest42 lacks "fail" call when operation unexpectedly succeeds

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.10.1.1
• Fix Version/s: 10.10.1.1
• Component/s: JDBC, Test
• Assignee: Richard N. Hillegas
• Reporter: Dag H. Wanvik
• Created: 22/Feb/13 03:35
• Updated: 03/Sep/14 08:31
• Resolved: 27/Feb/13 13:07

Description

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 ); }

}

Issue Links

• relates to: DERBY-6000 Implement support for JDBC 4.2