3 ms·

Yes! Additionally, it hurts users when the data is changing beneath them. Rows can appear twice or disappear as you move between pages.

• layer8 5y ago
  As a user, I’d rather live with that possibility than not being able to jump to a page in random-access fashion.
  • pmontra 5y ago
    As a user I like paged results when I sort by a key (maybe a timestamp) and want to look at the records around the one I found. However in a large dataset I always use a search filter. As a developer without a specific requirement if the time is short (it always is) I create a paged navigation using the defaults of the framework I'm using. Then the customer might or might not ask for a search filter. If frameworks defaulted on search filters I'd give customers them first and paged navigation if requested.
  • Andys 5y ago
    OK, but how many pages is too many? I can understand what you're saying for say, 1 to 20 pages, but it doesn't make any sense to me to go to hundreds, or worse, thousands of pages.