Search

check what you are putting into iTotalDisplayRecords it should be the recordcount after filtering, not the number of rows you have returned in the json.

else, and the sorting, filtering ++ will be done in

effects both sorting and filtering. What you can do

number, the display length, filtering ) to the server side.

that all the sorting / filtering etc is done by

it). Also how would filtering cope with null data,

I'm not sure what "aoSearchAndSortByElements" is trying to do? You can define an initial filtering using oSearch: http://datatables.net/usage/options#oSearch Allan

Without bServerSide:true, then you don't need to return iTotalRecords etc - since all the sorting / filtering etc is done on the client side. See these two pages for the difference: http://datatables.net/examples/data_sources/ajax.html http://datatables.net/examples/data_sources/server_side.html Regards, Allan

expressions to do complex filtering such as NOT and

well as subsequent sorts (filtering seems to remain quick