db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-821) Client driver: Implicitly close exhausted result sets on the server
Date Mon, 29 Jun 2009 14:39:47 GMT

     [ https://issues.apache.org/jira/browse/DERBY-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dag H. Wanvik updated DERBY-821:
--------------------------------

    Derby Categories: [Performance]

> Client driver: Implicitly close exhausted result sets on the server
> -------------------------------------------------------------------
>
>                 Key: DERBY-821
>                 URL: https://issues.apache.org/jira/browse/DERBY-821
>             Project: Derby
>          Issue Type: Improvement
>          Components: Network Client, 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: changes.html, DERBY-821-v2.diff, DERBY-821-v2.stat, DERBY-821.diff,
DERBY-821.stat
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message