We were unable to get the Search function to work with a large returned data set (about 2300 rows). From scanning the other tickets I found that the Search function does not work when the returned data set is greater than 2000 rows.
An offer was made to increase the number of rows the table will search via a code patch. We would like to take advantage of this offer as well.
Also, we anticipate that our typical user will typically download greater than 2000 rows. Please recommend the best way to handle large data sets where we need to do searches from the browser.
If you are using some complicated queries for making wpdatatables and your MySQL-query based wpDataTable doesn’t work correctly with server-side processing, probably this is happening because wpDataTables server has problems with parsing of the query and building new queries dynamically (happens rarely, but does sometimes). To avoid this please prepare a MySQL view (a stored query), which will return the data that you need, call it e.g. “view1” and then build a wpDataTabled based on a simple query like “SELECT * FROM view1″.
Also if you are using database name in query like this:
SELECT * FROM database_name.table_name
Please use separate mysql connection and then remove that database_name from the query.
We were unable to get the Search function to work with a large returned data set (about 2300 rows). From scanning the other tickets I found that the Search function does not work when the returned data set is greater than 2000 rows.
An offer was made to increase the number of rows the table will search via a code patch. We would like to take advantage of this offer as well.
Also, we anticipate that our typical user will typically download greater than 2000 rows. Please recommend the best way to handle large data sets where we need to do searches from the browser.
Mark Lee
Hi Mark,
Thank you for your purchase.
If you are using some complicated queries for making wpdatatables and your MySQL-query based wpDataTable doesn’t work correctly with server-side processing, probably this is happening because wpDataTables server has problems with parsing of the query and building new queries dynamically (happens rarely, but does sometimes). To avoid this please prepare a MySQL view (a stored query), which will return the data that you need, call it e.g. “view1” and then build a wpDataTabled based on a simple query like “SELECT * FROM view1″.
Also if you are using database name in query like this:
SELECT * FROM database_name.table_name
Please use separate mysql connection and then remove that database_name from the query.
Kind Regards,
Isidora Markovic
wpDataTables: FAQ | Facebook | Twitter | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Amelia demo sites | Docs
You can try our wpDataTables add-ons before purchase on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables
Hi Milan,
Perhaps you misunderstand. I am looking for the same code modifications offered in PUBLIC TICKET #1378452.
Please have a look there and let me know.
Mark
HI Mark,
Can you please send a query that you use for making this table?
Kind Regards,
Isidora Markovic
wpDataTables: FAQ | Facebook | Twitter | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Amelia demo sites | Docs
You can try our wpDataTables add-ons before purchase on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables