Passing Pagination details around

[eluser]steelaz[/eluser]
Could you use table name as prefix to session var, this way multiple tables would have their own cached queries.

[eluser]theswede[/eluser]
I did it the session way, it seems simpler than creating an extra table. Ah, a library. Brilliant! I should think more OOP and less ugly code.

[eluser]GDmac - expocom[/eluser]
adamp1: "... after say, they modify a record."
To return to a filtered view (or just to store filter settings), why not
use a hidden field in the edit-form with some "returnToPage..." or
"cameFromPage" information you can use to show the next step.
- (make sure you do not INSERT INTO the database all the formfields,
sanatize and validate! :-)

[eluser]adamp1[/eluser]
Problem is you still have to pass this data to the form to put it in the hidden filed. Which complicates the URL, and when using pagination as well it gets more complicated.

[eluser]CI shocki[/eluser]
I expanded the pagination class a bit so it does accept GET parameters. I found for filtering this is the best option. Even if some people dont't like it. In some situatione GET is still the easiest solution and used by most web apps by the way...