Received: from as.tksoft.com (gyw.com [209.55.67.177] (may be forged)) by hub.org (8.9.3/8.9.3) with ESMTP id OAA46160 for ; Fri, 29 Oct 1999 14:22:00 -0400 (EDT) (envelope-from tjk@tksoft.com) Received: (from tjk@tksoft.com) by uno.tksoft.com (8.8.8/8.8.8) id LAA24162; Fri, 29 Oct 1999 11:12:50 -0700 From: "tjk@tksoft.com" Message-Id: <199910291812.LAA24162@uno.tksoft.com> Subject: Re: [SQL] trivial problem To: raanders@altoplanos.net (Roderick A. Anderson) Date: Fri, 29 Oct 1999 11:12:49 -0700 (PDT) Cc: oleg@sai.msu.su, pgsql-sql@postgreSQL.org In-Reply-To: from "Roderick A. Anderson" at Oct 29, 99 10:07:16 am Content-Type: text If limit didn't mean "get first 50," there would be no time/effort saved by specifying a limit. I.e. when a limit is specified, the backend looks for matches until it finds 50 records, and then stops. Troy > > On Fri, 29 Oct 1999, Oleg Bartunov wrote: > > > select * from table order by column limit 50 > > > > It used to be and could still be in Oracle (sorry to pull them into this) > that limit applied to the selection clause so the first 'n' tulples > selected,not the top/bottom 'n', would be reported. > Would this be a feature of the SQL standard or of Oracles > implementation? And how does PostgreSQL handle limits? > > Rod > -- > Roderick A. Anderson > raanders@altoplanos.net Altoplanos Information Systems, Inc. > Voice: 208.765.6149 212 S. 11th Street, Suite 5 > FAX: 208.664.5299 Coeur d'Alene, ID 83814 > > > ************ > >