On Sat, Sep 15, 2012 at 7:06 PM, will trillich
will.trill...@serensoft.comwrote:
Hi Francisco --
I'm not talking about paginating a resultset, I'm talking about returning
to a previously-established resultset on some future HTTP request. Here's
the scenario:
You are asking just how to
Roger that -- so: include the search params in the links, and recreate the
recordset each time via ...-search({},{}). Sounds reasonable.
Off to the salt mines...
On Sun, Sep 16, 2012 at 10:07 AM, Bill Moseley mose...@hank.org wrote:
On Sat, Sep 15, 2012 at 7:06 PM, will trillich
User enters some search parameters (location, date-range, etc). Gets 500
results which we paginate. Once the user pages to the item of interest,
he/she can then click thru to edit or see more detail.
It'd be nice to have 'breadcrumbs' that *take the user back to that page of
that search*.
What's
Some databases provide means to return a specific set of records, and even an
offset,
In DBIx::Class, when you search, you can actually specify the page as an
option [1],
if you're not querying against a database, you might want to use something like
Memcached or the like to store your
Hi Francisco --
I'm not talking about paginating a resultset, I'm talking about returning
to a previously-established resultset on some future HTTP request. Here's
the scenario:
12:01 Bob submits search form for Chicago between 1-Apr-2012 and
30-Apr-2012
12:02 Bob sees first page of results,
I've used temporary tables for large search results I've needed to get back
to quickly and didn't want to rebuild from scratch...
On Sat, Sep 15, 2012 at 7:06 PM, will trillich
will.trill...@serensoft.comwrote:
Hi Francisco --
I'm not talking about paginating a resultset, I'm talking about
Steve --
Does that work when someone starts a search and then goes to lunch and
comes back the next day to click next? Do you key it to the session ID
somehow?
On Sat, Sep 15, 2012 at 9:21 PM, Rippl, Steve rip...@woodlandschools.orgwrote:
I've used temporary tables for large search results
To be honest this was on a low use internal app, and a new search would
trigger cycling the temp table. I just threw this out there, but sure, you
could key it by session or perhaps have multiple temp tables depending on
traffic, and I'm sure you'd have to clean them up after some period,
again
