Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 65779 invoked from network); 5 Jul 2005 18:41:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 5 Jul 2005 18:41:19 -0000 Received: (qmail 2151 invoked by uid 500); 5 Jul 2005 18:41:17 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 2127 invoked by uid 500); 5 Jul 2005 18:41:17 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 2113 invoked by uid 99); 5 Jul 2005 18:41:16 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jul 2005 11:41:16 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [32.97.182.143] (HELO e3.ny.us.ibm.com) (32.97.182.143) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jul 2005 11:41:17 -0700 Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by e3.ny.us.ibm.com (8.12.11/8.12.11) with ESMTP id j65IfAaS024175 for ; Tue, 5 Jul 2005 14:41:10 -0400 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay04.pok.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id j65IfAL3182456 for ; Tue, 5 Jul 2005 14:41:10 -0400 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.12.11/8.13.3) with ESMTP id j65If9cr017274 for ; Tue, 5 Jul 2005 14:41:09 -0400 Received: from [127.0.0.1] (bandaram.svl.ibm.com [9.30.40.139]) by d01av03.pok.ibm.com (8.12.11/8.12.11) with ESMTP id j65If8VX017057 for ; Tue, 5 Jul 2005 14:41:09 -0400 Message-ID: <42CAD3DA.6010707@Sourcery.Org> Date: Tue, 05 Jul 2005 11:39:22 -0700 From: Satheesh Bandaram User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Derby Discussion Subject: Re: Does Derby optimize queries w/ ORDER BY and "LIMIT"? (w/ indexes?) References: <20050705171621.3235610FB2B8@asf.osuosl.org> <42CAC6BA.5030207@sbcglobal.net> In-Reply-To: <42CAC6BA.5030207@sbcglobal.net> X-Enigmail-Version: 0.85.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii 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 As far as I know, Derby doesn't optimize based on maxRows. This is only used to limit rows returned to clients, as you mentioned below. Satheesh Mike Matrigali wrote: >I'll start by saying that I am not an optimizer expert. I don't think >the optimizer does anything special with limits - but I could be wrong, >maybe someone else with more knowledge in that area can let us know. > > > >