Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 25984 invoked from network); 27 Mar 2009 13:53:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 27 Mar 2009 13:53:15 -0000 Received: (qmail 33484 invoked by uid 500); 27 Mar 2009 13:53:15 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 33441 invoked by uid 500); 27 Mar 2009 13:53: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 33433 invoked by uid 99); 27 Mar 2009 13:53:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Mar 2009 13:53:15 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Mar 2009 13:53:12 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 4A634234C056 for ; Fri, 27 Mar 2009 06:52:51 -0700 (PDT) Message-ID: <416891160.1238161971303.JavaMail.jira@brutus> Date: Fri, 27 Mar 2009 06:52:51 -0700 (PDT) From: "Bryan Pendleton (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-3842) Convert "org.apache.derbyTesting.functionTests.tests.store.holdCursorExternalSortJDBC30.sql" to junit. In-Reply-To: <627133149.1218961666394.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689902#action_12689902 ] Bryan Pendleton commented on DERBY-3842: ---------------------------------------- I don't think the precise location of the commit or of the sort buffer size matters, because the sorting occurs before the first record has been retrieved, so as long as the commit is after the first record has been retrieved, whether the overflow-to-disk occurred on the 4th or 5th record doesn't really matter. What matters is that the commit doesn't close and release the temporary sorted records; that would cause some sort of internal error fetching records after the commit if it occurred. Ideally, the test would verify that the sort actually *did* overflow to disk; I think there is some information in the runtime statistics that will prove this. You could also verify that external sorting occurred by watching the sorter's behavior in the debugger, I suppose. > Convert "org.apache.derbyTesting.functionTests.tests.store.holdCursorExternalSortJDBC30.sql" to junit. > ------------------------------------------------------------------------------------------------------ > > Key: DERBY-3842 > URL: https://issues.apache.org/jira/browse/DERBY-3842 > Project: Derby > Issue Type: Test > Components: Test > Reporter: Junjie Peng > Assignee: Tiago R. Espinha > Attachments: derby-3842-1.patch, derby-3842-1.stat, derby-3842-tiago.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.