[ http://issues.apache.org/jira/browse/DERBY-821?page=comments#action_12363814 ]
Knut Anders Hatlen commented on DERBY-821: ------------------------------------------ Answer to my own question about why QRYCLSIMP is disabled when LMTBLKPRC is used: The DB2 driver seems to send QRYCLSIMP=1 in the OPNQRY message, but it closes the result set explicitly with a CLSQRY anyway. My best guess is that the disabling has something to do with this. I will modify the network server so that it disables QRYCLSIMP when the DB2 driver is used and the protocol is LMTBLKPRC, and enables it for the client driver (also when LMTBLKPRC is being used). > 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 > > 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
