db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Wilder (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-821) Client driver: Implicitly close exhausted result sets on the server
Date Tue, 31 Jan 2006 18:52:33 GMT
    [ http://issues.apache.org/jira/browse/DERBY-821?page=comments#action_12364666 ] 

Philip Wilder commented on DERBY-821:

I'm sorry I just noticed this now Knut but I should bring it to your attention that you are
in fact undoing work that was done in DERBY-213. The decision to remove the implicit close
from the Client Driver ResultSets was to bring the Derby Client in line with the embedded
driver which does not close ResultSets implicitly. Also there is an outstanding jira issue
(DERBY-545) that asks the question as to what the Client should do. I would ask that if you
come to a concrete conclusion the you also address DERBY-545 when you close this issue.

I will be monitoring DERBY-821 for a few days if you would like anything clarified.

> 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:
>     Reporter: Knut Anders Hatlen
>     Assignee: Knut Anders Hatlen
>     Priority: Minor
>      Fix For:
>  Attachments: 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:
For more information on JIRA, see:

View raw message