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 Wed, 01 Feb 2006 13:17:48 GMT
    [ http://issues.apache.org/jira/browse/DERBY-821?page=comments#action_12364799 ] 

Knut Anders Hatlen commented on DERBY-821:

Thanks for commenting on this issue, Philip.

>From my reading of DERBY-213 and DERBY-545, it seems like the term
"implicit closing" has a different meaning in those issues. Before the
DERBY-213 fix, forward-only result sets on the client were closed when
the cursor was positioned after the last row. DERBY-213 and DERBY-545
call this behaviour "implicit closing".

The implicit closing I am talking about, happens only on the network
server. The result set will be open on the client until close() is
called explicitly, hence the application won't see any changes in
behaviour. None of the test cases you added in DERBY-213 fail, e.g.,
next() still returns false instead of throwing an exception after last

> 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