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:02:44 GMT
     [ http://issues.apache.org/jira/browse/DERBY-349?page=all ]

Bryan Pendleton updated DERBY-349:
----------------------------------

    Derby Info: [Patch Available]

Patch is ready now, I believe.

Also, a typo in my last comment: this patch deletes the jdk14 master, not the jdk15 master.
The svn stat should make it clear.

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

>   Components: Network Client, Network Server
>     Versions: 10.1.1.0
>     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,
jdk16-master.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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message