You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Bernt M. Johnsen (JIRA)" <de...@db.apache.org> on 2006/02/13 13:49:45 UTC
[jira] Resolved: (DERBY-821) Client driver: Implicitly close
exhausted result sets on the server
[ http://issues.apache.org/jira/browse/DERBY-821?page=all ]
Bernt M. Johnsen resolved DERBY-821:
------------------------------------
Resolution: Fixed
Committed revision 377367.
> Client driver: Implicitly close exhausted result sets on the server
> -------------------------------------------------------------------
>
> Key: DERBY-821
> URL: http://issues.apache.org/jira/browse/DERBY-821
> 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-821-v2.diff, DERBY-821-v2.stat, DERBY-821.diff, DERBY-821.stat, changes.html
>
> Forward-only result sets that are exhausted should be implicitly
> closed on the server. This way, ResultSet.close() does not have to
> send an explicit close message generating unnecessary network traffic.
> The DRDA protocol supports this. From the description of OPNQRY (open
> query):
> The qryclsimp parameter controls whether the target server
> implicitly closes a non-scrollable query upon end of data (SQLSTATE
> 02000) in association with the cursor type.
--
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