[ http://issues.apache.org/jira/browse/DERBY-1292?page=comments#action_12378226 ]
Bryan Pendleton commented on DERBY-1292: ---------------------------------------- The use of a collection of type information with an entry for each batch element appears to be the solution chosen by the embedded driver. Here is a comment from the addBatch() method in EmbedPreparedStatement.java: //get a clone of the parameterValueSet and save it in the vector //which will be used later on at the time of batch execution. //This way we will get a copy of the current statement's parameter //values rather than a pointer to the statement's parameter value //set which will change with every new statement in the batch. So this feels like the correct solution to pursue in the client. > ClassCastException in ClientDriver when using CLOB columns and batch updates > ---------------------------------------------------------------------------- > > Key: DERBY-1292 > URL: http://issues.apache.org/jira/browse/DERBY-1292 > Project: Derby > Type: Bug > Versions: 10.1.2.1 > Reporter: Gerald Khin > Assignee: Bryan Pendleton > > java.lang.ClassCastException: java.lang.String > at > org.apache.derby.client.net.NetStatementRequest.computeProtocolTypesAndLengths(Unknown > Source) > at > org.apache.derby.client.net.NetStatementRequest.buildSQLDTAcommandData(Unknown > Source) > at org.apache.derby.client.net.NetStatementRequest.writeExecute(Unknown > Source) > at > org.apache.derby.client.net.NetPreparedStatement.writeExecute_(Unknown Source) > at org.apache.derby.client.am.PreparedStatement.writeExecute(Unknown > Source) > at > org.apache.derby.client.am.PreparedStatement.executeBatchRequestX(Unknown > Source) > at org.apache.derby.client.am.PreparedStatement.executeBatchX(Unknown > Source) > at org.apache.derby.client.am.PreparedStatement.executeBatch(Unknown > Source) > at CCEBatchUpdateRepro.doInserts(CCEBatchUpdateRepro.java:71) > at CCEBatchUpdateRepro.main(CCEBatchUpdateRepro.java:27) -- 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
