X-Original-To: pgsql-sql@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id D2E93474E53 for ; Mon, 17 Feb 2003 11:25:03 -0500 (EST) Received: from technovell.com (213-97-10-232.uc.nombres.ttd.es [213.97.10.232]) by postgresql.org (Postfix) with ESMTP id D309F474E42 for ; Mon, 17 Feb 2003 11:25:02 -0500 (EST) Received: from technovell.com pgsql@technovell.com [195.55.249.227] by technovell.com with NetMail SMTP Agent $Revision: 3.16 $ on Linux; Mon, 17 Feb 2003 17:26:21 +0100 Message-ID: <3E510D04.5EEC1808@technovell.com> Date: Mon, 17 Feb 2003 17:25:40 +0100 From: Terry Yapt X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: pgsql-sql@postgresql.org Cc: Tom Lane Subject: Re: rownum References: <20030215045410.15935.qmail@web12707.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200302/371 X-Sequence-Number: 11769 Perhaps you are using ROWNUM like LIMIT/OFFSET... http://www.postgresql.org/docs/view.php?version=7.3&idoc=1&file=queries-limit.html I hope this helps... chester c young wrote: > > > Considering that it can trivially be done on the client side, I think > > it would be a hard sell to put such a wart into the protocol ... > > having used Oracle for many years, I cannot think of a project in which > I did not use rownum, including within procedures and triggers and > subqueries. can usually be easily done - loop within loop - but more > easily and bugfree as column within select. > > by "wart" do you mean aesthetically or code-wise? naively, it seems > like pg is already keeping a row counter to implement limit.