Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 35988 invoked from network); 6 Mar 2009 04:04:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Mar 2009 04:04:04 -0000 Received: (qmail 46635 invoked by uid 500); 6 Mar 2009 04:04:03 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 46609 invoked by uid 500); 6 Mar 2009 04:04:03 -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 46596 invoked by uid 99); 6 Mar 2009 04:04:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Mar 2009 20:04:03 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [63.82.107.6] (HELO red.amberpoint.com) (63.82.107.6) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Mar 2009 04:03:55 +0000 Received: from [127.0.0.1] (bp-laptop.edgility.com [10.10.13.2]) by red.amberpoint.com (8.13.8/8.13.8) with ESMTP id n2643WDS030488 for ; Thu, 5 Mar 2009 20:03:32 -0800 Message-ID: <49B0A093.3060403@amberpoint.com> Date: Thu, 05 Mar 2009 20:03:31 -0800 From: Bryan Pendleton User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Derby Discussion Subject: Re: Order the results, *and* slice them References: <49B093E7.8020608@nuix.com> In-Reply-To: <49B093E7.8020608@nuix.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org > Both of these give an error at ORDER BY. Am I doing something wrong, or > is this a missing part of the ROW_NUMBER() feature? I think you might be seeing DERBY-3634: http://issues.apache.org/jira/browse/DERBY-3634 I think there is some renewed work on the ROW_NUMBER feature for Derby 10.5, so hopefully some of these problems will be addressed soon. bryan