4 ms·
That is exactly what I came here to say as well. In my datatable custom query layer, I can pull down 1 million rows and view them instantly displaying them in a
by kardianos 3y ago
That is exactly what I came here to say as well. In my datatable custom query layer, I can pull down 1 million rows and view them instantly displaying them in a continuous list on the client, lazy load related table rows, and neither the web client nor the traditional web server on a traditional SQL Server, where I dynamically build the queries and can filter on any column, break a sweat. And the server is on 10 year old hardware that still runs spinning disks and the clients are often older lower powered computers. And that's with me not optimizing performance, other then thinking about it lightly up front.
EDIT: Yes, the tables are sometimes medium wide, 20-50 columns buffered on the client on those rows.
- DrScientist 3y agoI think because their whole original logic was client side - to generate a filtered view would require loading all the data in the client first and then applying a filter.
- kardianos 3y agoOr just re-query the server with the new filters applied.