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 Tue, 07 Feb 2006 04:50:57 GMT
    [ http://issues.apache.org/jira/browse/DERBY-821?page=comments#action_12365387 ] 

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

I looked at the server side Changes:
Regarding the JCC check in DRDAStatement, Bryan said
>  perhaps it's worth
> looking at this a little while longer, to see if there is a way to handle
> this without having to add the session pointer to the database object; maybe
> you could instead arrange to pass the session pointer as an argument when
> you call isRSCloseImplict?

I think it would be better to just have it take a boolean and centralize the differences for
AppRequesters in AppRequester.java  with supportXXX() methods there.   In this case, If we
can get the JCC side fixed the condition will have to be modified further to include version
info.  It is best to have that all in one place I think. 

There was a question on negative testing for protocol.  There is a test testProtocol.java
which has a file protocol.tests where you can put tests for protocol sequences that will never
actually be sent from the client.





> 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