Return-Path: <ramzam@tenbit.pl>
Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list cocoon-users@xml.apache.org
Received: (qmail 51749 invoked from network); 23 Jan 2001 21:18:31 -0000
Received: from twardziel.tenbit.pl (HELO tenbit.pl) (195.205.163.235)
  by h31.sny.collab.net with SMTP; 23 Jan 2001 21:18:31 -0000
Received: from [213.77.101.245] (HELO bill)
  by tenbit.pl (CommuniGate Pro SMTP 3.2.4)
  with SMTP id 8448506 for cocoon-users@xml.apache.org;
 Tue, 23 Jan 2001 22:18:27 +0100
Message-ID: <002901c08582$0062ede0$1b64a8c0@bellstream>
From: "Roman Zamorski" <ramzam@tenbit.pl>
To: <cocoon-users@xml.apache.org>
References: <F116Oq3JkrKdMUPqRnS000016dc@hotmail.com>
Subject: Re: ESQL and max-rows / skip-rows attributes
Date: Tue, 23 Jan 2001 22:18:12 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-2"
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

> >By looking at the code, it seems that for each execution of a
> ><esql:connection> the underlying query is always executed. Only during
> >insertion of the sql results into the current DOM tree the
> ><esql:max-rows> and <esql:skip-rows> are used to define the range of
> >records (skip-rows, skip-rows + max-rows] to be inserted.
> >
> >As this can easily get very expensive for complex queries, I am looking
> >for an alternative way to 'cache' long results as returned by the esql

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;

r.