The jQuery plugin used for table rendering (http://www.tablefixedheader.com/) supports pagination, but only on the client-side. So if you have millions of records on the server you'd still have to transfer and store a prohibitive amount of data on the browser.
The solution is then to create our own pagination scheme, where we only pull a relatively small number of records (say, 500) from the server at a time. Whether or not we can integrate this behavior with the plugin built-in pagination UI I'm not sure. We might have to create our own pagination UI.
The jQuery plugin used for table rendering (http://www.tablefixedheader.com/) supports pagination, but only on the client-side. So if you have millions of records on the server you'd still have to transfer and store a prohibitive amount of data on the browser.
The solution is then to create our own pagination scheme, where we only pull a relatively small number of records (say, 500) from the server at a time. Whether or not we can integrate this behavior with the plugin built-in pagination UI I'm not sure. We might have to create our own pagination UI.