You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Bryan Pendleton (JIRA)" <de...@db.apache.org> on 2006/04/01 19:31:27 UTC
[jira] Commented: (DERBY-349) setByte() with executeBatch causes
hang with client if mapping is invalid, e.g. setByte to DATE
[ http://issues.apache.org/jira/browse/DERBY-349?page=comments#action_12372791 ]
Bryan Pendleton commented on DERBY-349:
---------------------------------------
I have convinced myself that the original problem described by this bug is no longer present in the product, and there are just some test problems that need to be cleaned up. The test problems include:
- The disabled tests for the client need to be turned back on. This is easy; I just need to delete the code that disabled those tests. One question is whether to delete all the no-longer-needed "if (executeBatchTests)" blocks, or just delete the little section at the head of the setXXX() method and leave the boolean executeBatchTests variable present, but always set to TRUE. I am leaning toward cleaning up all the dead code, even though it's a larger diff.
- When the client gets a data conversion error in executeBatch, it wraps the actual exception in a BatchUpdateException. However, the judge_setXXX method in parameterMapping.java doesn't grok this, and so I need to enhance it to crawl through the exception chain looking for the actual data conversion exception of interest.
- Then I need to carefully examine the new output, to ensure that it is safe to update the master file.
- Lastly, unfortunately, there are a whole bunch of master files for this test. There are variations for different JVMs, different JDBC drivers, etc. Yuck. I think I'll have to crawl though a bunch of them. Unfortunately, I don't have access to all those JVMS and drivers, so I may need help from the community.
Still, the bottom line is good news: when I'm done, we'll have more tests running, and easier-to-read result files.
And one less open bug. :)
> 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
>
> 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