Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1106111007.1142471398824.JavaMail.jira@ajax>
Date: Thu, 16 Mar 2006 01:09:58 +0000 (GMT)
From: "Dag H. Wanvik (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Closed: (DERBY-992) A corner case bug and missing
 optimization in ScrollInsensitiveResultSet
In-Reply-To: <1499104101.1140021189129.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-992?page=all ]
     
Dag H. Wanvik closed DERBY-992:
-------------------------------


verified that the bug is now gone on trunk.

> A corner case bug and missing optimization in ScrollInsensitiveResultSet
> ------------------------------------------------------------------------
>
>          Key: DERBY-992
>          URL: http://issues.apache.org/jira/browse/DERBY-992
>      Project: Derby
>         Type: Bug
>   Components: JDBC
>     Versions: 10.0.2.1
>  Environment: Solaris 10/x86, Sun VM 1.4.2
>     Reporter: Dag H. Wanvik
>     Assignee: Dag H. Wanvik
>     Priority: Minor
>      Fix For: 10.2.0.0
>  Attachments: Main.java, derby-992-1.diff, derby-992-1.stat
>
> a) For a scrollable, insensitive result set (read-only) which is
>    empty, ResultSet#afterLast should have no effect, but erroneously
>    sets the internal variable afterLast to true, so that a sunsequent
>    call to ResultSet#isAfterLast will return 'true' in the embedded
>    client. It does not happen on the client driver, because it seems
>    to do some double book-keeping for this case.
> b) In ScrollInsensitiveResultSet#getNextRowCore and #getAbsoluteRow,
>    there are missing checks will cause unnecessary read (attempts)
>    from underlying result set even if end has been seen already.
>  Both would be nice to fix in preparation for DERBY-690...   

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