Danimal wrote: > Matt, > > I find that the best is to just reset to the beginning with any change > of sort or pagination. It's too confusing not to. For example, if you > are showing 5 records per page in a 50 record set and you are on page > 4, then you suddenly switch to 25 records per page, what should it do? > Throw an error (there is no page 4 anymore)? Or have you on page 2? Or > back to page 1? > > And with sorting, if I'm on page 4 of 7 pages sorted by last name, > then suddenly switch to sorting by first name, staying on page 4... at > least to me... is more confusing than just reverting back to page one. > Of course, you could stay on page 4 with the new sort. So sorting > seems to be more of a design choice. But pagination changes: go back > to page 1. > > -Danimal
Hi, thanks for the reply. I agree that there are some cases where it should reset the page or the sort. OTOH picture this: I'm on page 1 and I sort by hostname ASC, it gives me the hostnames starting at A etc. Then I want to move through this sorted list so I go to page 2, and my sort has been reset because I can't work out how to modify the links generated by paginating_find. I'm not fiddling with the page size yet so that isn't an issue, and it probably should go back to page 1 if I change the sort order, however I really would think that keeping the sort order when changing pages is kinda important. I might be going mad with this so let me know if i'm babbling :P Thanks Matt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
