https://bugs.documentfoundation.org/show_bug.cgi?id=149984
--- Comment #2 from Pierre Fortin <[email protected]> --- (In reply to Rafael Lima from comment #1) > I think this might impact performance on very large tables. Agreed; but the status line is updated with the count of selected rows. Seems like that counting code would be the best place to count each unique entry; then sorting by count should be no worse than: Filter by Condition>{Top,Bottom} 10 Thanks for considering. We daily deal with script-generated .csv files which have to be limited to 1M rows; so having 16M rows is a HUGE improvement for us. That reduces the amount of file splitting we have to do. Our worst case .csv is over 75M records; but now having 16M rows will do until CPU horsepower and memory get much better. :) -- You are receiving this mail because: You are the assignee for the bug.
