[DERBY-1766] Make test jdbcapi/batchUpdate run in client/server framework

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 10.2.1.6
• Component/s: Test
• Labels: derby_triage10_8
• Environment: Any
• Urgency: Low
• Issue & fix info: Newcomer
• Assignee: Unassigned
• Reporter: Oystein Grovlen
• Created: 28/Aug/06 08:53
• Updated: 17/Feb/11 23:02

Description

The test jdbcapi/batchUpdate.java is disabled in the DerbyNetClient
framework. The reason seems to be that you get a general exception,
BatchUpdateException, instead of the specific exceptions you get in
the embedded framework. The fix for this is probably to unwrap the
BatchUpdateException to get to the more specific exception.

Since batchUpdate.java does not run in client/server, DERBY-1292 has
added a test to derbynet/prepStmt.java that really belongs in
batchUpdate. As part of fixing this JIRA, that test, and other
similar tests in prepStmt, should be moved to batchUpdate.

It also seems like parameterMapping.java had similar problems
which was changed by changing the canon to expect
BatchUpdateExceptions. In my opinion, one should also unwrap the
BatchUpdateExceptions in that test.