db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-1766) Make test jdbcapi/batchUpdate run in client/server framework
Date Thu, 17 Feb 2011 23:03:12 GMT

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

Myrna van Lunteren updated DERBY-1766:

    Issue & fix info: [Newcomer]
             Urgency: Low
              Labels: derby_triage10_8  (was: )

Marking newcomer as the remaining task - moving the test cases for batches from the ParameterMappingTest
(there's no batch stuff in PreparedStatementTest) to the BatchUpdateTest - ought to be fairly
easy. But the tests are running where they are, so giving this low priority.
Or do we like them better in the ParameterMappingTest? After all, they're parameter mapping
test cases too...And perhaps there's less code duplication if we leave them where they are...

> 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
>              Labels: derby_triage10_8
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message