[ http://issues.apache.org/jira/browse/DERBY-822?page=comments#action_12376757 ]
Kathey Marsden commented on DERBY-822: -------------------------------------- I noticed that on the day of this checkin, lang/simpleScroll.sql, and lang/scrollCursors1.sql with JCC 2.5 (56) started failing with a protocol error. The test is ok with JCC 2.4(17), JCC 2.5 (36) and JCC 2.6 (90) are all ok. I am not sure yet if this is some sort of regression with our DRDA handling or a bug with this particular verison of JCC. I will post more info as I have it. Here is the diff for scrollCursors1 *** Start: scrollCursors1 jdk1.5.0_02 DerbyNet derbynetmats:jdbc20 2006-04-18 23:37:03 *** 392a393 > ERROR 58017: The DDM parameter value is not supported. DDM parameter code > point having unsupported value : 0x2102 394 del I 395 del < ----- 396 del < 2 396a395 > IJ ERROR: Unable to establish cursor 398 del < I 399 del < ----- 400 del < 3 400a397 > IJ ERROR: Unable to establish cursor 402 del < 1 row inserted/updated/deleted 402a399 > ERROR (no SQLState): invalid operation: connection closed > Client driver: Pre-fetch data on executeQuery() > ----------------------------------------------- > > Key: DERBY-822 > URL: http://issues.apache.org/jira/browse/DERBY-822 > Project: Derby > Type: Improvement > Components: Network Server, Performance > Versions: 10.2.0.0 > Reporter: Knut Anders Hatlen > Assignee: Knut Anders Hatlen > Priority: Minor > Fix For: 10.2.0.0 > Attachments: DERBY-822-v1.diff, DERBY-822-v1.stat, DERBY-822-v2.diff, > DERBY-822-v2.stat, DERBY-822-v3.diff, DERBY-822-v3.stat > > Currently, the client driver does not pre-fetch data when > executeQuery() is called, but it does on the first call to > ResultSet.next(). Pre-fetching data on executeQuery() would reduce > network traffic and improve performance. > The DRDA protocol supports this. From the description of OPNQRY (open > query): > The qryrowset parameter specifies whether a rowset of rows is to be > returned with the command. This is only honored for non-dynamic > scrollable cursors (QRYATTSNS not equal to QRYSNSDYN) and for > non-scrollable cursors conforming to the limited block query > protocol. The target server fetches no more than the requested > number of rows. It may fetch fewer rows if it is restricted by extra > query block limits, or if a fetch operation results in a negative > SQLSTATE or an SQLSTATE of 02000. -- 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
