db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-821) Client driver: Implicitly close exhausted result sets on the server
Date Thu, 02 Feb 2006 17:13:05 GMT
     [ http://issues.apache.org/jira/browse/DERBY-821?page=all ]

Bryan Pendleton updated DERBY-821:

    Attachment: changes-no-object-tags.html

Hi Knut Anders,

Your document is excellent. Thank you very much for writing it. The changes make much more
sense to me now. My browser (Firefox) was not behaving so well with the <object> tags
in your changes.html file, so I took the liberty of re-posting the file with the <object>
tags removed, in case there are other people having the same problem.

> 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-no-object-tags.html, 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