Thanks, Jeff. What I’m actually looking for though is a way to prevent the database from return the full set in the first place, i.e. there’s a half a gig of data I don’t want in the wire or in CF memory. As far as I can tell the paging control does not affect what gets selected (and returned) -- only what’s displayed. If a person does something stupid, like say asks for a list of every hit on the site this year, I want to top that request out 2000 hits before it saturates my network and bogs my RAM.

 

As far as I know since CF doesn’t use cursors, the only way to do that in CF is to limit the max recs in SQL, I just can find a good place to put that code modification.

 

Michael Caulfield
Webmaster, College Relations Office
Keene State
College
603-358-2101


From: Jeff Fleitz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 05, 2005 5:35 PM
To: [email protected]
Subject: Re: [plum] TOP-ping a query

 

Hi Michael,

When you build a list via the Plum IDE, there is an option for the number of rows to display per page (this is the rowsPerPage attribute in the DisplayList custom tag. It defaults to 50, but you can set it to something else. I have pretty much settled on 10-20 per page, so that my users don't have to scroll the list.   So if you have 2000 records and your rowsPerPage is 20, you are going to have 20 pages.  A paging control is set at the bottom of the list to allow you to navigate between pages.  See the DisplayList tag in the help file.

You can either use a standard search form that filters the list, or you can build a list with an embedded search form on it.  Either way the rowsPerPage attribute is going to dictate how many rows come back at a time.

Also take a look at the included PlumContentItemList.cfm template in the admin/content directory.  This shows how to use an embedded search form on a list, while not returning any rows for the first hit.

HTH,

Jeff

Caulfield, Michael wrote:

I have a hit log db, a huge thing, I wanted to use the plum search, list & view interface. However, I need to reduce the amount of records coming back (not only the records displayed, the actual records coming back from the db). My home grown version topped the records at 2000 ala SELECT TOP 2000 blah, blah.

 

What’s the cleanest way to accomplish this in Plum?

 

TIA,

 

Michael Caulfield
Webmaster, College Relations Office
Keene State
College
603-358-2101

********************************************************************** You can subscribe to and unsubscribe from lists, and you can change your subscriptions between normal and digest modes here: http://www.productivityenhancement.com/support/DiscussionListsForm.cfm **********************************************************************

Reply via email to