Hi Mike I can't think of any easy solution, unfortunately.
You _could_ use search_for_ids instead of search, which then returns an array of IDs, which is much lighter to store in the session, but this is only an option if doing searches on a single model. And when you get to the end of a page, you're still going to have to know the query details as well. Good luck getting something working. Cheers -- Pat On 28/01/2009, at 3:17 AM, mike castleman wrote: > > hello, > > I'm sure there's an obvious solution to this, but I can't figure out > what it is. > > After the user performs a query, they are taken to an index page with > their results. Then, they can click on a result to go to a detail page > for that object. I would like the user to be able, from the detail > page, to be able to click a 'next' or 'previous' button to go to the > next or previous search result. > > I imagine I have to include the search query in the detail page URL > (ick) and/or store some kind of data about the query (and maybe its > current state or something?) in the session. > > Anyone have any ideas? > > Thanks a lot, > mlc > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Thinking Sphinx" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/thinking-sphinx?hl=en -~----------~----~----~----~------~----~------~--~---
