[DERBY-822] Client driver: Pre-fetch data on executeQuery()

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.2.1.6
• Fix Version/s: 10.2.1.6
• Component/s: Network Server
• Issue & fix info: Release Note Needed
• Bug behavior facts: Performance
• Assignee: Knut Anders Hatlen
• Reporter: Knut Anders Hatlen
• Created: 18/Jan/06 19:52
• Updated: 30/Jun/09 16:12
• Resolved: 18/Apr/06 13:55

Description

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.

Sub-Tasks

• Make tests less sensitive to pre-fetching: Closed