db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-349) setByte() with executeBatch causes hang with client if mapping is invalid, e.g. setByte to DATE
Date Sun, 02 Apr 2006 17:00:44 GMT
     [ http://issues.apache.org/jira/browse/DERBY-349?page=all ]

Bryan Pendleton updated DERBY-349:

    Attachment: derby-349-stat-with-jdk16.txt

Thanks, Knut, that was fast!

The jdk1.6 results look great, and I've incorporated the masterfile update into the patch.

Did you have any other comments or feedback on the patch?

As I looked at it again, I see now that the JDK1.4 and JDK 1.5 result files are identical,
so I don't think this test needs a separate jdk1.4 result file. So I've changed the patch
to delete the jdk1.5 result file.

Attached are 'derby-349-stat-with-jdk15.txt' and 'derby-349-diff-with-jdk16.txt'. The new
patch proposal adds the jdk1.6 master file update, and issues 'svn del' on the jdk1.4 master
file, rather than updating it.

I'll mark this issue "Patch Available", because I think it's ready to go now.

> setByte() with executeBatch causes hang with client if mapping is invalid, e.g. setByte
> -----------------------------------------------------------------------------------------------
>          Key: DERBY-349
>          URL: http://issues.apache.org/jira/browse/DERBY-349
>      Project: Derby
>         Type: Bug

>   Components: Network Client, Network Server
>     Versions:
>     Reporter: Daniel John Debrunner
>     Assignee: Bryan Pendleton
>     Priority: Minor
>  Attachments: derby-349-diff-with-jdk16.txt, derby-349-stat-with-jdk16.txt, derby-349-testFixes.diff,
> setByte() followed by an addBatch() and then an executeBatch causes a hang.
> May apply to any setXXX call that will result in any invalid conversion, possibly only
those conversions handled by the client.
> See the test jdbcapi/parameterMapping, look for this bug number in the code, to see the
cases disabled when running with the client.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message