Re: Problem with shownext

This WebDNA talk-list message is from

2003


It keeps the original formatting.
numero = 53013
interpreted = N
texte = Kenneth Grome wrote: > But when the same template is used on the live server, all the shownext > links above 500 are not shown, which makes it IMPOSSIBLE to page thru > all 1400 records. Instead, the only visible shownext links are the ones > that will display the first 500 found items. > That is the way that MaxFound has _always_ worked, it is the way that it is _documented_ to work, and the way that makes most sense. Set the MaxFound on the production site to a higher value. MaxFound and ShowNext are two different ways to make sure that you don't dump your entire database into a single page. MaxFound protects you against people running trivial searches (e.g. all records containing 'A') and bringing your web server to it's knees trying to generate a multimegabyte HTML file (not to mention bring the browser to a halt trying the render that large page). ShowNext, on the other hand, is intended to display small, byte-sized chunks of a much larger data set. If you are using ShowNext on your results pages, you should always set MaxFound to a high enough value to reasonably cover your largest possible search sets. ShowNext will efficiently display a limited window of records. If you use ShowNext, there is no real reason to set MaxFound to a small value, since you can always limit the return set to a reasonable size. But if you do this, you need to /always/ use ShowNext, so that you never have an uncontrolled return set. John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4720 Boston Way Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5747 ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Problem with shownext ( Jesse Williams-Proudman 2003)
  2. Re: Problem with shownext ( Kenneth Grome 2003)
  3. Re: Problem with shownext ( Donovan 2003)
  4. Re: Problem with shownext ( Kenneth Grome 2003)
  5. Re: Problem with shownext ( John Peacock 2003)
  6. Re: Problem with shownext ( Donovan 2003)
  7. Re: Problem with shownext ( Tim Robinson 2003)
  8. Problem with shownext ( Kenneth Grome 2003)
Kenneth Grome wrote: > But when the same template is used on the live server, all the shownext > links above 500 are not shown, which makes it IMPOSSIBLE to page thru > all 1400 records. Instead, the only visible shownext links are the ones > that will display the first 500 found items. > That is the way that MaxFound has _always_ worked, it is the way that it is _documented_ to work, and the way that makes most sense. Set the MaxFound on the production site to a higher value. MaxFound and ShowNext are two different ways to make sure that you don't dump your entire database into a single page. MaxFound protects you against people running trivial searches (e.g. all records containing 'A') and bringing your web server to it's knees trying to generate a multimegabyte HTML file (not to mention bring the browser to a halt trying the render that large page). ShowNext, on the other hand, is intended to display small, byte-sized chunks of a much larger data set. If you are using ShowNext on your results pages, you should always set MaxFound to a high enough value to reasonably cover your largest possible search sets. ShowNext will efficiently display a limited window of records. If you use ShowNext, there is no real reason to set MaxFound to a small value, since you can always limit the return set to a reasonable size. But if you do this, you need to /always/ use ShowNext, so that you never have an uncontrolled return set. John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4720 Boston Way Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5747 ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ John Peacock

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

2.0Beta Command Ref (can't find this instruction) (1997) retain raw [cart] submitted value (2004) Online reference (1997) Review comparison by PC Magazine: Open for On-line Business (1997) WebCat2 - Getting to the browser's username/password data (1997) Orderfile Info is Dissappearing (1998) Deleting Orders (1997) Location of Browser Info.txt file (1997) Emailer file formats (1998) [movefile] (1999) range searching (1998) URGENT: Can't email orders - HELP #2 (1998) OT - ImageMagick on MacOS X (2004) [showif] question (2000) Date Question (2002) Part Html part WebDNA (1997) SSL do I need it?? (1998) syntax question, not in online refernce (1997) [CART] (1997) Colors in cart (2002)