db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-821) Client driver: Implicitly close exhausted result sets on the server
Date Mon, 06 Feb 2006 04:26:10 GMT
    [ http://issues.apache.org/jira/browse/DERBY-821?page=comments#action_12365237 ] 

Kathey Marsden commented on DERBY-821:
--------------------------------------

Bryan posted some questions on the list.  I put the link here for reference.

http://www.nabble.com/DERBY-821-comments-t1065371.html

I have not had an opportunity  to review the patch but hope to do so tomorrow.  I was wondering
if you had tested 10.1/10.2 client/server combinations.  If there is special logic needed
for JCC, I am guessing it might also be needed for older clients and ODBC, but just a guess
as I have not yet looked at the patch.





> 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.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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message