David Siedband wrote:
What I'm looking for is an efficient approach for creating persistence for either the parameters of the search or the result set. Here are some of the techniques I've cosidered:
[1] Store previous SQL query as text and concatenate the new and/or logic.
Hurm :-S
[2] Store the unique IDs of the existing result set in an array and filter results of next search for presence in the array.
Hurm :-S
[3] Massive generic zSQL method with handling for all parameters ...using a bunch of <dtml-if parameter> and <dtml-if "_.hasattr(parameter, 'sort')"> to switch on and off the different arms of this query. Persistence of search parameters through sessions
That's what I'd go for...
or <input type="hidden"... (this seems like it has way to much overhead, are there any benefits to
Yuk.
this approach?)
Yeah, minimal storage of stuff on the server per user... cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk