Return-Path: Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 24802 invoked from network); 25 Jan 2001 20:39:41 -0000 Received: from twardziel.tenbit.pl (HELO tenbit.pl) (195.205.163.235) by h31.sny.collab.net with SMTP; 25 Jan 2001 20:39:41 -0000 Received: from [213.77.101.245] (HELO bill) by tenbit.pl (CommuniGate Pro SMTP 3.2.4) with SMTP id 8586496 for cocoon-users@xml.apache.org; Thu, 25 Jan 2001 21:39:42 +0100 Message-ID: <029001c0870e$777322a0$0b64a8c0@bellstream> From: "Roman Zamorski" To: References: Subject: Re: ESQL and max-rows / skip-rows attributes Date: Thu, 25 Jan 2001 21:36:16 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > On Tue, 23 Jan 2001, Roman Zamorski wrote: > > > there is also an alternative way of doing this by using of SQL 'LIMIT' > > command. > > LIMIT maxrows || LIMIT skiprows,maxrows > > you can put it at the end of the query statement like this: > > > > select * from table limit 10,20; > > another comment on this - it looks like postgresql and mysql use the exact > opposite order of values when a comma is used. ugh. is there a standard > way this clause _should_ appear? > aaaaaaaaaaaaaaaaaaaaa! I see - the standards are for disobeying ;)