Bug in 'searchCols' option + a suggestion
Bug in 'searchCols' option + a suggestion
MeiR_ct
Posts: 2Questions: 0Answers: 0
I inspected the ajax request of table loading with serverSide set to true, and with escapeRegex set to false inside searchCols.
I found out that the request doesn't set columns[x][search][regex] in the request heder to be true, until I set regex to true as well, inside searchCols (which is not documented).
Also, in addition to (or instead of) searchCols, I would suggest an option to set search inside columns for initial filtering. I consider it as much more clear, rather than defining bunch of columns, and then defining another bunch of searchCols that match respectively, with plenty of null values in unneeded columns.
This discussion has been closed.
Replies
Hi,
Thanks for the feedback and the bug report. That certainly is a bug!
Agreed! I really dislike my current implementation... With 1.11 search is going to get an overhaul. I'll look into addressing this then, and the bug before then :-)
Allan
Hi Allan. Thanks for the fast response!
Waiting for the new search implemention. :)
I'm wondering, is there any way to subscribe to new version releases?
There is the Release feed. I need to look at making an e-mail list for it as well!
Allan