https://datatables.net/extensions/fixedheader/examples/options/columnFiltering.html
https://datatables.net/reference/api/column().search()
적용 문제..
https://stackoverflow.com/questions/58497592/datatable-column-filtering-not-working-server-side
-> 나랑 똑같은 질문인데 답없음..
https://phppot.com/demo/column-search-in-datatables-using-server-side-processing/
Additionally the callback is passed in the JSON data received from the server when Ajax loading data, which can be useful for configuring components connected to your table, for example Editor fields.
기본 예제 테이블로는 column filtering 잘됨
내 테이블로 컬럼 필터링이 안된다!!
헤더까진 제대로 된다.
검색 input에 넣으면 검색이 않된다.
I've created this little example which demonstrates how it might be done: http://live.datatables.net/piqidoqo/1/edit .
One key element is to use the initComplete callback - this is important for Ajax sourced tables since they are of course asynchronous by definition.
By definition Server Side Processing means that all sorting, searching and paging functions are performed by the server.
Even if it were possible to use client side filtering it would only affect the data at the client, which is the page being displayed.
It is not possible to use client side filtering with server side processing enabled.
The problem is that you're using serverSide processing - this means that only the rows being displayed are sent to the client,
so when you build your dropdown list in the initComplete function,
you will only ever see items sent for that very first page.
serverSide is only really needed if you have thousands of records, if you don't, and the dropdowns are more important, just remove that initialisation option.
즉, serverside옵션은 오직 서버에서 보낸 row만 출력한다.
백날 javascript상에서 search() 함수 적용 후 draw() 해도 안 된다.
search() 하면, serverside로 ajax 요청 보냄. POST element의 [search] value만 바뀌어서.