Search and server side processing

Search and server side processing

baronrobertbaronrobert Posts: 2Questions: 1Answers: 0
edited April 14 in Free community support

Hello,
I use datables2 and server side processing to fetch data.

I want to use the search feature to filter quickly data from the fetched results (like we can do when using data js array as source).
It seems that when using server side processing Search feture try to fetch data on server to fill new filtered data in the Table.

Is there a way to make "search" feature to look in already downloaded data and prevent it to request the server ?

Thanks
BR.

Answers

  • kthorngrenkthorngren Posts: 22,451Questions: 26Answers: 5,163

    When server side processing is enabled the client side search functionality is disabled as all of the table processing is expected to take place at the server. With server side processing the only data downloaded to the client are the rows shown on the page. If you have 10 rows displayed on a page, for example, then using client side searching would only search in those 10 rows.

    Possibly you don't need server side processing and can just use ajax to initially fetch all of the data? Do you have performance impacts without server side processing?

    Kevin

  • baronrobertbaronrobert Posts: 2Questions: 1Answers: 0
    edited April 15

    Fetching all data from server is not an option as it take too long time to get data (around 10ms per items, 5000items total.

    Whe user fetch part of data, server send back around 10 cols per row. Using "quick" search on this data will be very convenient for users to filter or get an even smaller set of results. Without overloading one more time from server.

    I understand how "search" feature works, and that is no cache option available.
    Maybe will be added later if some more user need it.

    Thanks for your help :)

Sign In or Register to comment.