Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Developers List" <torque-dev@db.apache.org>
Received-SPF: pass (herse.apache.org: domain of greg.monroe@dukece.com
 designates 152.3.166.24 as permitted sender)
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C767CF.EAAA005C"
Subject: RE: Finding position of previous selected record in new ordering
Date: Fri, 16 Mar 2007 09:35:08 -0400
Message-ID: <8F5843B903F59D4C8C6806BB49A3911902BB2726@dukece-mail3.dukece.com>
In-Reply-To: <0765101BA5724F4DAC1607B4CF4BC1714C2561@scuderia09.vps.local>
Thread-Topic: Finding position of previous selected record in new ordering
Thread-Index: AcdnprPACMyjEK23SoueWpTCqU1WBQAJ1l5w
References: <0765101BA5724F4DAC1607B4CF4BC1714C2561@scuderia09.vps.local>
From: "Greg Monroe" <Greg.Monroe@DukeCE.com>
To: "Apache Torque Developers List" <torque-dev@db.apache.org>

------_=_NextPart_001_01C767CF.EAAA005C
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

You can use Criteria.setOffset to define the start point and
Criteria.setLimit
to define the number of records to return.  This gets translated into
the=20
appropriate DB server specific select.  But test and verify that it work

with your specific DB since there were issues with various DB prior to
3.3 (but I think they have been worked out now).
=20
Also, you might look at the LargeSelect utility class.  This does the=20
same thing but also has some performance/ease of use enhancements=20
like caching serveral pages, being able to select by page, supplying=20
page counts and the like.


________________________________

	From: Tobias Hilka [mailto:thilka@vps.de]=20
	Sent: Friday, March 16, 2007 4:40 AM
	To: Apache Torque Developers List
	Subject: Finding position of previous selected record in new
ordering
=09
=09
	Hello everyone,
	=20
	we are facing the following problem:
	=20
	We have a grid with many entries (up to several 100 000
entries). For performance reasons we only select the window which is
visible for the user (about 50 entries). The rest of the grid is
initialized with null-Items. So far so good.
	=20
	But now our problem: If we do order the grid by firstname
ascending and select the fith entry, then we order the by the same
column descending, we want the selection to persist and therefore we
want the selection window to contain the selected entry in its new
environment (e.g. position 99 950 to 100 000 and select record number 99
996).
	=20
	Is there any possibility to express this in torque? We know
about some special features of some databases which can handle this. And
I think there are features in SQL 2003 for this.
	=20
	=20
	Thank you for your help.
	=20
	=20
	Tobias


Duke CE Privacy Statement
Please be advised that this e-mail and any files transmitted with it are =
confidential communication or may otherwise be privileged or =
confidential and are intended solely for the individual or entity to =
whom they are addressed.  If you are not the intended recipient you may =
not rely on the contents of this email or any attachments, and we ask =
that you  please not read, copy or retransmit this communication, but =
reply to the sender and destroy the email, its contents, and all copies =
thereof immediately.  Any unauthorized dissemination, distribution or =
copying of this communication is strictly prohibited.


------_=_NextPart_001_01C767CF.EAAA005C--