db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-821) Client driver: Implicitly close exhausted result sets on the server
Date Mon, 23 Jan 2006 14:49:10 GMT
    [ http://issues.apache.org/jira/browse/DERBY-821?page=comments#action_12363677 ] 

Knut Anders Hatlen commented on DERBY-821:

In the network server code, DRDAResultSet.isRSCloseImplicit() has this

 * Method to decide weather the ResultSet should be closed implicitly.
 * When the protocol type is Limited Block Query Protocol we should not
 * close implicitly even if qryclsimp is set to YES.

I haven't found anything in the DRDA spec saying that result sets
should not be implicitly closed when the protocol is Limited Block
Query Protocol. Enabling implicitly closing for the LBQ protocol does
not seem to break anything.

Does anyone know why implicitly closing of result sets is disabled for
the Limited Block Query Protocol?

> 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:

> 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