[Maypole] Searching and paged results

Jesse Sheidlower jester@panix.com
Tue, 4 May 2004 22:48:18 -0400


This is another one for the category of I-don't-know-how-to-process-args,
I think.

In the current default setup, a search will be paged if there
is a value for rows-per-page set. However, the actual search
parameters are not passed to the pager for construction of a
new URL.

Thus, for example, if you have a database with 1,000 beers, of which
400 are IPAs, and you execute a search for "IPA", the first screen
will have 10 (or whatever rows-per-page is) IPAs. But when you click
on "[2]", you won't get the second page of 400 IPAs, but rather the
second page of 1,000 beers.

This should probably go into the category of Wrong, as opposed to
Could-Be-Done-Differently. It's also probably more broadly applicable
than just the pager--various links to or from search results might
need to take this into account.

I guess the solution will involve always appending form params
back onto the query? But will that complicate things if one is
expecting form params instead of URL params?

Jesse Sheidlower, beta-ing away