Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <12445746.1156771588301.JavaMail.jira@brutus>
Date: Mon, 28 Aug 2006 06:26:28 -0700 (PDT)
From: "John H. Embretsen (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-1766) Make test jdbcapi/batchUpdate run in
 client/server framework
In-Reply-To: <12883799.1156755204713.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

     [ http://issues.apache.org/jira/browse/DERBY-1766?page=3Dall ]

John H. Embretsen updated DERBY-1766:
-------------------------------------

    Summary: Make test jdbcapi/batchUpdate run in client/server framework  =
(was: Make test jdbcapi/batachUpdate run in client/server framework)

> Make test jdbcapi/batchUpdate 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: 10.2.1.0
>         Environment: Any
>            Reporter: =C3=98ystein Gr=C3=B8vlen
>            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.

--=20
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: htt=
p://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira