Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 7D49247546C for ; Thu, 8 Aug 2002 16:11:27 -0400 (EDT) Received: from smaug.securitymatrix.com (unknown [64.238.98.87]) by postgresql.org (Postfix) with ESMTP id A84E2475452 for ; Thu, 8 Aug 2002 16:11:26 -0400 (EDT) Received: from kaos.securitymatrix.com (kaos.securitymatrix.com [172.16.0.101]) by smaug.securitymatrix.com (8.11.6/8.11.6) with ESMTP id g78KDEW02491 for ; Thu, 8 Aug 2002 16:13:29 -0400 Subject: Table Sorting and Limit Question From: Dawn Hollingsworth To: pgsql-sql@postgresql.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 08 Aug 2002 16:10:38 -0400 Message-Id: <1028837453.4754.1.camel@kaos> Mime-Version: 1.0 X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200208/156 X-Sequence-Number: 9002 Currently we have a table with a sequence number( id ) as a primary key, a date field which is indexed and several other columns. The user interface allows the user to sort the data by date and limits the result set to 100 rows. The question is: The user interface needs the capability to sort the table by date but pull out the hundred row set that contains id say...542 for example. What would be the best way to do this taking into account this table is several hundred thousand rows? Dawn Hollingsworth Principal Engineer AirDefense, Inc.