some I found:
In most cases, I don't think it's inefficient to perform the find again and sort by that column. It may seem counter intuitive, but an html page doesn't have a live connection to the database, so it has to request data from the server again anyway.
Thank you, Beverly!
Thank you, Mike!
My database has about 2000 records in all with images and videos, but only five text columns are shown on the web.
It is also an exciting news for me that searching again won't be bad!
So it seems that I'd better to do the search again.
the 'answer' to this topic, depends on how many records are returned. limiting the number of records in a table display is advisable on the web regardless of the method(s) used to get them to the browser. this is simply the rendering of tables. tall tables take longer.
and yes, the sorts should be on the entire find whether you return the first "X" or all of them to the browser for viewing.
It's definitely to do JS only pagination and sorting. One example can be found here:
Click on the column headers for sorting.
This was done with FM PHP API and YUI library (which, unfortunately, isn't continued anymore by Yahoo).
Of course, the database has to return the complete found set. But it works fairly well also for larger sets: