[
http://issues.apache.org/jira/browse/DERBY-428?page=comments#action_12371436 ]
Bryan Pendleton commented on DERBY-428:
---
I've committed this patch: http://svn.apache.org/viewcvs?rev=387895view=rev
NetworkClient PreparedStatement.executeBatch()
[
http://issues.apache.org/jira/browse/DERBY-428?page=comments#action_12366899 ]
Bryan Pendleton commented on DERBY-428:
---
I believe that the 2-byte limit to the number of correlated commands in a
single DRDA request is a hard limit.
I've thought of
[
http://issues.apache.org/jira/browse/DERBY-428?page=comments#action_12366904 ]
Kathey Marsden commented on DERBY-428:
--
Bryan said
I've thought of two possible ways to proceed:
1) The network client could refuse to execute a batch of more than 64K
Kathey Marsden (JIRA) wrote:
If I understand this correctly, if we go with 1) would the workaround
just be for the user to break up their batches into a few batches each
with less than 64K statements?
Yes, exactly so.
If so, I think 1) is fine for now.
Great! That's the path I'll
[
http://issues.apache.org/jira/browse/DERBY-428?page=comments#action_12366874 ]
Bryan Pendleton commented on DERBY-428:
---
The crash on batch element 65535 seems pretty straightforward: correlation IDs
in DSS blocks are 2-byte unsigned integers, so of
[
http://issues.apache.org/jira/browse/DERBY-428?page=comments#action_12330002 ]
Gregory W. Inns commented on DERBY-428:
---
We're getting one similar to this one, but only sporadically.
Does anyone know a workaround for it?
NetworkClient
[
http://issues.apache.org/jira/browse/DERBY-428?page=comments#action_12314877 ]
Bernt M. Johnsen commented on DERBY-428:
BTW: When the BatchUpdateException is thrown, the connection is closed down
(probably due to the
