Return-Path: <tom@obsess.com>
Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list cocoon-users@xml.apache.org
Received: (qmail 25682 invoked from network); 2 May 2000 09:58:07 -0000
Received: from obsess.com (root@195.26.32.100)
  by locus.apache.org with SMTP; 2 May 2000 09:58:07 -0000
Received: from localhost (tom@localhost)
	by obsess.com (8.9.3/8.9.3) with ESMTP id KAA08549
	for <cocoon-users@xml.apache.org>; Tue, 2 May 2000 10:55:45 +0100
Date: Tue, 2 May 2000 10:55:44 +0100 (BST)
From: tom stuart <tom@obsess.com>
To: cocoon-users <cocoon-users@xml.apache.org>
Subject: Re: is <sql ... skip-rows="{@next}"> possible?
In-Reply-To: <390EA442.35AC7036@interface-business.de>
Message-ID: <Pine.LNX.4.10.10005021049010.7653-100000@obsess.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

On Tue, 2 May 2000, Thomas Guettler wrote:

> The following code does not work. {@skip} gets ignored.
>   <query connection="www_odbc" max-rows="2" skip-rows="{@skip}">  
> Has some one an idear how to achieve this without xsp?
> Why works the {@foo} inside the query, but not in the attributes?:

I can't speak authoritatively about the SQLProcessor (I haven't looked at
the source yet) but presumably it only does this parameter interpolation
on the contents of the <query> tag (ie. your query), but not the tag
attributes. This makes a certain kind of sense, since you can redefine the
variable-left-delimiter and variable-right-delimiter with the <query> tag
attributes, which would make interpolation on the attributes themselves a
bit self-referential.

The only obvious solution I can see is to implement the skip-rows
functionality directly in your SQL query, as in:

	SELECT * FROM person WHERE id={@id} LIMIT {@skip},10

which will select 10 rows starting from row (skip+1).

I know this works with MySQL; YMMV.

-Tom