We are using the driver profile more, and the CommandQueryExecutor sets that for the different types of queries.
Currently the TableRowSorter sets the driver page size using query builder techniques - it calls CommandQueryExecutor.executeReadAllPages which uses the table-read driver profile. It should use a dedciated driver profile so we can better control the settings when we know we want to read all the pages.
Follow on from #1677
We are using the driver profile more, and the CommandQueryExecutor sets that for the different types of queries.
Currently the TableRowSorter sets the driver page size using query builder techniques - it calls CommandQueryExecutor.executeReadAllPages which uses the table-read driver profile. It should use a dedciated driver profile so we can better control the settings when we know we want to read all the pages.