Received: from candle.pha.pa.us (candle.navpoint.com [162.33.245.46] (may be forged)) by mail.postgresql.org (8.11.3/8.11.1) with ESMTP id f2KLKfH98522 for ; Tue, 20 Mar 2001 16:20:41 -0500 (EST) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id QAA17359; Tue, 20 Mar 2001 16:19:20 -0500 (EST) From: Bruce Momjian Message-Id: <200103202119.QAA17359@candle.pha.pa.us> Subject: Re: Re: Use of the LIMIT clause ? In-Reply-To: <12832.985122976@sss.pgh.pa.us> "from Tom Lane at Mar 20, 2001 04:16:16 pm" To: Tom Lane Date: Tue, 20 Mar 2001 16:19:20 -0500 (EST) CC: Richard Poole , pgsql-sql@postgresql.org X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200103/400 X-Sequence-Number: 2068 > Bruce Momjian writes: > > Is this a TODO item? Seems we should match MySQL, seeing as we took the > > feature syntax from them. > > Question is, will more people be inconvenienced if we change it than if > we leave it alone? Seems like someone gets screwed either way ... No question about it. One solution would be to disable this syntax for one release and then fix it in the one after that. We already offer LIMIT/OFFSET, which is what they should be using anyway. If we can't remember, and no one reported the bug for many releases, odds are no one was using that more limited form anyway. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026