Search

I think it purely depends upon the VIEW and what it is doing (hundreds of sub-queries for example would be bad). It certainly won't be less efficient than hitting the db with 300 individually compiled and executed queries though. Allan

I think because you're explicitly asking for a record, it's ignoring the fact that it's not on that page. Probably the easiest way would be to do something like this: if ( table.rows({page: 'current'}).ids().toArray().includes('id_1')){ $('#tiger').css('visibility','visible'); } See here, Colin

Hi @akwebapps , We include links to the documentation for SearchPanes for each of the platforms that are supported (as below). From there you are within the documentation for the relevant Editor Library. Full documentation for the platforms we support is available here: - .NET - NodeJS - PHP From there you can find the install instructions through a link on the navigation pane on the left side. I guess we thought this would have been fairly clear, I'll talk to the other guys and see what they think though. Thanks, Sandy

@kthorngren Thank you. That worked :)

It would be worth looking at SearchPanes or SearchBuilder, otherwise you could do something like this: http://live.datatables.net/cusologu/7/edit Colin

Looks like you have colspan in the tbody. Datatables doesn't support this. The HTML docs provide the specs for this. Kevin

Yep, see searchDelay, Colin

Thanks for the answer, Allan! I read the server side manual carefully and noticed the errors you mentioned. In addition, the amount of records at the moment does not require a server side, as you also mentioned. I am now using client side. Thanks again!

We're happy to take a look, but as per the forum rules, please link to a test case - a test case that replicates the issue will ensure you'll get a quick and accurate response. Information on how to create a test case (if you aren't able to link to the page you are working on) is available here. Cheers, Colin

Yep, as tangerine said, just a simple test case on http://live.datatables.net/ that demonstrates the issue would be the best way to move this forward. It doesn't need any complexity, just the minimum to reproduce the errors. Colin