Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 98265 invoked from network); 24 May 2006 14:10:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 24 May 2006 14:10:23 -0000 Received: (qmail 69830 invoked by uid 500); 24 May 2006 14:10:17 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 69536 invoked by uid 500); 24 May 2006 14:10:15 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 69288 invoked by uid 99); 24 May 2006 14:10:13 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 May 2006 07:10:13 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 May 2006 07:10:12 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id F04AE7141FA for ; Wed, 24 May 2006 14:09:31 +0000 (GMT) Message-ID: <14966660.1148479771981.JavaMail.jira@brutus> Date: Wed, 24 May 2006 14:09:31 +0000 (GMT+00:00) From: "Andreas Korneliussen (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Closed: (DERBY-1276) Calling ResultSet.isLast() on a scrollable insensitive resultset, causes the entire ResultSet to be populated In-Reply-To: <20996132.1146561646415.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/DERBY-1276?page=all ] Andreas Korneliussen closed DERBY-1276: --------------------------------------- Thanks for committing. Closing this report since it is a minor issue, which is resolved on 10.2 trunk. If anyone want to port it to the 10.1.3 branch (and have a hard time porting this issue), please reopen the issue, and let me know if you want me to consult. > Calling ResultSet.isLast() on a scrollable insensitive resultset, causes the entire ResultSet to be populated > ------------------------------------------------------------------------------------------------------------- > > Key: DERBY-1276 > URL: http://issues.apache.org/jira/browse/DERBY-1276 > Project: Derby > Type: Improvement > Components: SQL > Versions: 10.2.0.0, 10.1.3.0 > Reporter: Andreas Korneliussen > Assignee: Andreas Korneliussen > Priority: Minor > Fix For: 10.2.0.0 > Attachments: DERBY-1276.diff, DERBY-1276.stat, derbyall_report.txt > > The following is not a bug, however some applications do not always need to scroll to the last row, however they do want to check isLast(). Therefore it is unfortunate that isLast() is expensive. The general logic in ScrollInsensitiveResultSet is to populate rows by demand. > The current logic in ScrollInsensitiveResultSet to return true or false on isLast(), is to move to the last row. If the last row is not the same row number as the current, then isLast() returns false. When moving to the last row, all rows will be populated into the BackingStoreHashtable of the ScrollInsensitiveResultSet. > This logic may be rewritten to only move to the next row. If the next row exists, isLast() may return false. > (note the logic is also optimized to use beforeFirst and afterLast flags) -- 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