Re: &max=

This WebDNA talk-list message is from

2003

It keeps the original formatting. numero = 52957
interpreted = N
texte = Alain Russell wrote:> By the way, I think that result is wrong> If I have a max=10 in a search the [numfound] should never be higher > than 10 in my opinion ..> The [numfound] should be a numerical value for the number of items that > will be looped through in a [founditems] ??One of the main uses for the max= is to split search results onto multiple pages.Something like:[SEARCH {searchparameters}&max=10]Found [NUMFOUND] items[FOUNDITEMS]{list first ten items}[/FOUNDITEMS]{link to next ten items}[/SEARCH]If the [NUMFOUND] value was limited to the max value, the only way to diplay the actual number of found items on the search results page would be to use a *separate* search for it, and that's hardly practical.Of course, a separata [NUMLISTED] (or whatever) tag with a value limited to the max= value, could come handy, but cosidering hw easy it is to work around the problem, I wouldn't say it's the most important addition to WebDNA.Frank Nordberghttp://www.musicaviva.com-------------------------------------------------------------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:

[WebDNA] Parsing JS value to WebDNA variable or (Palle Bo Nielsen 2018)