db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Øystein Grøvlen (JIRA) <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-1766) Make test jdbcapi/batachUpdate run in client/server framework
Date Mon, 28 Aug 2006 08:53:24 GMT
Make test jdbcapi/batachUpdate run in client/server framework

                 Key: DERBY-1766
                 URL: http://issues.apache.org/jira/browse/DERBY-1766
             Project: Derby
          Issue Type: Test
          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.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message