[jira] Commented: (DERBY-349) setByte() with executeBatch causes hang with client if mapping is invalid, e.g. setByte to DATE

["Bryan Pendleton (JIRA)" <de...@db.apache.org>]

    [ http://issues.apache.org/jira/browse/DERBY-349?page=comments#action_12369163 ] 

Bryan Pendleton commented on DERBY-349:
---------------------------------------

I tried re-enabling the test code in parameterMapping.java, and the result was that I did *not* get a hang, but rather got a blizzard of diffs involving parameter conversion errors, which seems to be the intended behavior of this test.

I also got similar results from writing a trivial 10 line standalone test program.

So those experiments seem to indicate that maybe this bug has already been fixed by some other change along the way over the last 9 months.

I'll double-check my results some more, to make sure that I'm not overlooking something.


> 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 Server, Network Client
>     Versions: 10.1.1.0
>     Reporter: Daniel John Debrunner
>     Assignee: Bryan Pendleton
>     Priority: Minor

>
> 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