Adding extra search callbacks for ColumnFilterWidgets

[pivotal-energy-solutions]

Adding extra search callbacks for ColumnFilterWidgets

[tiliv]

After having looked at how to configure ColumnFilterWidgets, I believe it's pretty much just building on existing dataTables.js APIs (i.e., it greatly simplifies the workflow provided by the per-column fnFilter API and adds some fanciness via drop-downs).

I'll need to look at how it interacts with requests made while bServerSide = true, though. Ideally, the DatatableView could extract those column-specific filters and apply them automatically.

[ScottEAdams]

Have you had a chance to look into this anymore? I will dig a little further into it in the coming weeks hopefully but in the meantime, perhaps you could give me some advice on whats the current simplest way to add column based filters?

[ScottEAdams]

After starting to create a pull request for this I basically came to the conclusion that this is going to be so different for every case that its just easier to do in the get_queryset and use the complex lookups of django to build the queries specifically for your column needs. Its working well for me. Here is an example that basically gives you the column index (ind) and the query string (real_query):

    getquery = self.request.GET
    sSearches = fnmatch.filter(getquery, 'sSearch_?')
    for sS in sSearches:
        sQuery = getquery.get(sS, '').strip()
        if sQuery:
            ind = int(sS.split('_')[1])
            real_query = re.search('\(^|,\)\((.*)\)\(,|$\)', sQuery)

[ivanlao]

is was reviewing this yesterday, you have to search for sSearch_[column_id] get parameter and apply and if the column type allow search, then search for it like is done in the table search.

A nice feature could be allow to add specific search for colums in the view, so you run the default search if the view has not defined an special search for that column. django-eztables and django-datatables-view has this feature.