[ http://issues.apache.org/jira/browse/DERBY-822?page=comments#action_12367192 ]
Knut Anders Hatlen commented on DERBY-822: ------------------------------------------ Created a sub-task (DERBY-1014) to make most of the test changes independent of the code changes in my previously attached patch (DERBY-822-v1.diff). Will attach a new (and smaller) patch to this issue later. > 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 Client, 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 > > 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
