[
https://issues.apache.org/jira/browse/DERBY-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-822:
--------------------------------
Derby Categories: [Performance]
> Client driver: Pre-fetch data on executeQuery()
> -----------------------------------------------
>
> Key: DERBY-822
> URL: https://issues.apache.org/jira/browse/DERBY-822
> Project: Derby
> Issue Type: Improvement
> Components: Network Server
> Affects Versions: 10.2.1.6
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Priority: Minor
> Fix For: 10.2.1.6
>
> 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.
-
You can reply to this email to add a comment to the issue online.
