Using searchCols for server-side processing on 1.10

ghukill

I've spent time recently familiarizing myself with Datatables, found the server-side approach perfect for our large results sets. But something I can't seem to trigger is searching / filtering on ONE column for the results set. The option searchCols looks perfect, but I can't seem to have it push values to columns[1][search][value], the column I'd like to search on.

Example code for searchCols:

$('#example').dataTable( {
"searchCols": [
    null,
    { "search": "My filter" },
    null,
    { "search": "^[0-9]", "escapeRegex": false }
  ]
} );

My code, thinking this array provided in searchCols would search the 2nd column:

$(document).ready(function(){           
    $('#example').DataTable( {      
        "serverSide": true,     
        "ajax": 'http://hostname-here/cgi-bin/php_simple.php',
        "searchCols":[          
            null,
            { "search" : "smalluser" }
        ]               
    } );    
});

Any suggestions? Am I missing something simple? I spent considerable time wrapping my head around the changes between 1.9 - 1.10, and decided to embrace the 1.10 as I hope to use this moving forward with my project. If I change the GET parameter "columns[1][search][value]=smalluser" manually, it behaves as expected; what am I missing about using searchCols as a parameter in launch?

Many thanks.

ghukill

I should clarify - I cannot get search terms to show up in the GET parameters using init options. When I enter them manually in a URL and hit the server-side script, it works beautifully. I've gotten "search":{"search":"smalluser"} to work, but that operates on all columns...

tangerine

Doesn't this suit your needs?

https://datatables.net/release-datatables/examples/api/multi_filter.html

ghukill

Thanks for responding. Unfortunately, I don't think so. I'd like to limit the records coming out of MySQL before they hit the browser. Let's say I've got 10,000 rows in SQL, I'd like to filter on a column and return let's say 1000 for a given user.

I could be wrong, but this looks like filtering client-side after the results set have been returned?

KenS

I am having the same issue. Defining "searchCols" does not seen to have any affect.

sectorad

I'm having the same problem.. searchCols does not seem to behave as expected.
There doesn't seem to be any way of setting initial per column search values when using server-side processing.

allan

It looks like there is an error with the Hungarian to camelCase translation for searchCols. Using the old Hungarian notation works: http://live.datatables.net/waselab/1/edit . I'll look into making the camelCase also work.

Allan

sectorad

Works like a charm. Thanks.

ghukill

Works like a charm indeed, thanks Allan.