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] Updated: (DERBY-1766) Make test jdbcapi/batchUpdate run in client/server framework
Date Tue, 30 Jun 2009 23:38:48 GMT

     [ https://issues.apache.org/jira/browse/DERBY-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Dag H. Wanvik updated DERBY-1766:

    Issue Type: Improvement  (was: Test)

> Make test jdbcapi/batchUpdate run in client/server framework
> ------------------------------------------------------------
>                 Key: DERBY-1766
>                 URL: https://issues.apache.org/jira/browse/DERBY-1766
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions:
>         Environment: Any
>            Reporter: Øystein Grøvlen
>            Priority: Minor
> 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.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message