Search

pulling the data via ajax for a single table,

after loading data via ajax, my click handler doesn't

Why are you sending the SQL query to the client? That would only be useful for debugging. And if there is a way of decoding it on the client-side, then the end user can decode it anyway. If you are worried about the client seeing the database column names, then change them in the JSON - have some kind of mapping. Although to be honest, if they can do damage with just knowing the column names, then there are bigger problems. I think @RichardD2 was perfectly clear in his first response. Use HTTPS to encrypt the communication between the client and server. Trying to encrypt so it can't easily be read in the browser's network inspector is utterly pointless in my opinion. The client-side must be able to decode it to be able to use it, so the client can decode it... Allan

Looks good - nice one! Thanks for the update :) Allan

The only real alternative at the moment is to fake the filtered count at the moment I'm afraid. At some point I would like to implement some kind of "until it is finished" pagination, but it isn't something that I've worked on yet. Allan

Thanks for pointing that out, Loren! It’s definitely useful to highlight the default behaviour of deferRender in DataTables 2.0. I'll amend accordingly. This will make optimizing large tables even easier without extra configuration. Appreciate the insight! Regards.

If anyone looking for solution, following worked for me: DataTablesCore.Api.register('responsive.resetChildCache()', function () { var responsive = this.context[0].responsive; responsive.s.childNodeStore = {}; }); Then your action: dataTable.value.dt.responsive.resetChildCache(); e.g on button click/ajax search etc.

Thanks a lot. It works great!

The sorting and filtering would be unaffected by ajax.reload(), but by default the paging is reset, so you'll return to the first page. If you want to remain on the same page, follow the second example on that reference page - it's demonstrating just that. The flicker is probably unavoidable if the data set is fairly large. On our 57 record examples, such as here, ajax.reload() doesn't flicker at all - as it's very quick to load and draw a small number of records. If the flicker is noticable, this section of the FAQ should help, it discusses various techniques to improve performance, Colin

As Kevin notes, Editor has multi-row editing built in. If you are using some other editing software, then you should contact the author of that software for support. Allan