CI Paging with searchresult

[eluser]adamp1[/eluser]
I forgot about uri_to_assoc, might have to try that solution, only problem is still passing all that data in the uri which can look messy.

The clean way is with sessions but how to handle it is hard, I was thinking of storing a hash of the controller and then storing all relevant filter options in an array. This way if you navigate from one pagination table to another it won't try and apply the old filter results to the new table, which would happen if you just stored the data globably.

Only thing is then is when should that data expire? Expire too soon and you might be searching and loose your filters, expire too late and when you come back and want a new search you still have the old settings.