Received: from athena.office.vi.net ([194.88.88.225]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f2DF85x34715 for ; Tue, 13 Mar 2001 10:08:05 -0500 (EST) (envelope-from rp@office.vi.net) Received: from rp by athena.office.vi.net with local (Exim 3.12 #1 (Debian)) id 14cqOu-0004RS-00; Tue, 13 Mar 2001 15:07:52 +0000 Date: Tue, 13 Mar 2001 15:07:52 +0000 From: Richard Poole To: pgsql-sql@postgresql.org Subject: Re: Re: Use of the LIMIT clause ? Message-ID: <20010313150752.A13549@office.vi.net> References: <3AADBFD7.D462E190@enseirb.fr> <7612.984439579@sss.pgh.pa.us> <3AAD785A.2DAEDCE@joystick.fr> <17374.984450118@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <17374.984450118@sss.pgh.pa.us>; from tgl@sss.pgh.pa.us on Mon, Mar 12, 2001 at 09:21:58PM -0500 X-Archive-Number: 200103/261 X-Sequence-Number: 1920 On Mon, Mar 12, 2001 at 09:21:58PM -0500, Tom Lane wrote: > Spy writes: > > Tom Lane a écrit : > >> Is that actually how MySQL interprets two parameters? We treat them > >> as count and offset respectively, which definition I thought was the > >> same as MySQL's. > > > But MySQL's syntax is different, as found on > > http://www.mysql.com/doc/S/E/SELECT.html : > > "SELECT [STRAIGHT_JOIN] [SQL_SMALL_RESULT] [SQL_BIG_RESULT] > > [SQL_BUFFER_RESULT] > > [...] > > [LIMIT [offset,] rows]" > > That's annoying; looks like we do it backwards from MySQL. Can anyone > confirm that this is how MySQL behaves (maybe it's a typo on this > documentation page)? Yes, it does behave as documented. > Should we consider changing ours if it is different? I don't know that it's worth it... it seems to inconvenience some people either way. I may soon be moving a moderately complex system from MySQL to Postgres and it wouldn't be the end of my world if I had to reverse all the LIMITs. Richard