I'm aware of the advantages and disadvantages of paginating table results, but I'm not sure what would be best in this particular case:
I have a table that can have between 0 and 1000 rows (sometimes more), and is constantly being updated from the server with new entries. Each row has about 10 columns, and each column can be used as a 'filter' (clicking on the label re-arranges rows ascending / descending according to that parameter).
My user will be constantly looking at this list, filtering and re-ordening rows in order to find entries. As there could be a huge number of results, I thought of two possibilities:
Paginating the results. Problem: If the table is constantly being updated, how do I keep it from moving elements up and down, and how do I keep the pagination consistent?
Never-ending scrolling. Problem: In most cases I would assume that, given enough filtering parameters, the user won't have to scroll down that much, so the desired result is probably in the top. But I can think of scenarios where the user might want to look for a result that, he knows, is roughly in the middle of the list (suppose he's ordering by date, or in my case by a Document Type).
Is there a third alternative for paginating tables that are constantly being updated?