[ http://issues.apache.org/jira/browse/DERBY-170?page=comments#action_12362883 ]
Kathey Marsden commented on DERBY-170: -------------------------------------- I checked in this change. Thanks Bryan for the patch. Date: Mon Jan 16 11:19:26 2006 New Revision: 369549 URL: http://svn.apache.org/viewcvs?rev=369549&view=rev One thing that would be good I think is to get more the great information in changes.html into the code comments. Of course the comments probably needn't contain as detailed an explanation as in the changes.html but a comment with the bug number pointing out the changes.html attached to the bug might be helpful to others looking at the code in the future. > Inserting large string value into non-existent table causes communication > link failure over Network Server. > ----------------------------------------------------------------------------------------------------------- > > Key: DERBY-170 > URL: http://issues.apache.org/jira/browse/DERBY-170 > Project: Derby > Type: Bug > Components: Network Server > Environment: Derby Network Server running with either JDBC or ODBC driver. > Reporter: A B > Assignee: Bryan Pendleton > Attachments: assert_repro.java, changes.html, storedProcs.java, > stored_proc_repro.java, svn_jan12_2006.status, svn_jan14_2006.diff > > The following failure, along with the 2 sub-tasks created under this issue, > are reproducible both from a JDBC client (JCC) and from an ODBC client (in > this case, DB2 Runtime Client). I've grouped them all together because they > all share the characteristic of "large data transfer", though the context in > which the transfer occurs is different for each failure. > Failure: When trying to insert a large string value (ex. 1 million chars) > into a non-existent table using a prepared statement, an ASSERT failure > occurs on the Derby side (because data size < 0), which leads to connection > closure and communication link failure. Note that the problem does NOT > happen if the target table actually exists. Repro can be found in the > "assert_repro.java" file attached to this bug. -- 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
