Hi Felix,

Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

-

I can see what the issue is.

Your table name has a space included - This will not work properly with our SQL Parser.

The only way to correctly call the SQL Table name that has spaces is to include those accent grave symbols around it (`) , so like :

SELECT * FROM `table name`.

But if you include the accent graves, then the filtering won't work with our server-side processing feature.

The solution ( if you need our server-side processing option enabled) is to rename your Table in the SQL Database.

Just change the spaces to anything else, like underscore.

Here is my example, my table was named "dummy employees" and that won't work properly;

so i rename it to "dummy_employees" and now our Plugin is filtering it without any issue.

Let me know how it goes, that should solve the issues.

Hi Felix,

If this is the screenshot of the current Query, I can see you are still having the accent grave symbols (`) around the Table name.

For the MySQL engine, we are dynamically adding the accent grave ( ` ), so there's no need to use it around the table name in the query. 

If you were to delete them, searching and filtering should be fixed.

So can you please try like this now :

SELECT * FROM Domestic_Substances_List(DSL)

and then the filtering should start working along with our server-side processing option.

Let me know if that helps.

Hi Felix,

Thank you for this feedback.

You are right, our SQL Parser seems to struggle if we use any bracket symbol "()" in the Table Name.

I also tried changing to other types of brackers, like squared [ or this one {  but it does not help/same result.

I am passing this to our Developers - they will do their best to improve the SQL Parser in order for it to accept these symbols as part of the table name, even though we can't promise an ETA on it.

For now, would it be possible for you to change your table name and not use any brackets?

I also tried with | symbols, that will not work, sadly.

For now, all I can come up with is using the underscores, so if i rename the SQL Table to Domestic_Substances_List_DSL

in that case, you can have our server-side processing to work along with filtering/search and no sorting issues in your Tables.

You can download my Video as a short demonstration here https://we.tl/t-kfO9okoCrG.

I am sorry for this inconvenience.

Let me know if that can work.

Thank you.

Hi Felix,

My apologies, I just recalled an alternate solution, forgot to mention it right away.

2. If you need to keep these brackets in the SQL Table Name, you will be able to have filtering/search/sorting to work, if you can disable server-side processing in your Table.

With our server-side processing disabled, then you can use the accent graves (`) around Table name without any filtering/search issues.

But then, with server-side option disabled -  you will not be able to activate any Editing, so keep that in mind.

Basically, it all comes down to server-side vs non-server-side.

 If your SQL query based tables are not bigger than 2.000 rows, 

you can disable server-side on SQL tables, and it will work like it does for Excel tables. ( loads all rows regardless of pagination)

If you need to increase the row count while still having the "toggle" to disable server-side,

Please go to ../wp-content/plugins/wpdatatables/source/class.wpdatatable.php and around line 3188 you'll see this:

if (is_array($res_dataRows) && count($res_dataRows) > 2000) {

The lines of code can change during Updates because our Developers add new lines from time to time, so it is best to search for the line in any Code Editor with CTRL+F to get the right line.

You can change the number 2000 to a value bigger than the number of rows in your table in order to still have that 'toggle option' for server-side processing.

Another PHP file in this path :

../wp-content/plugins/wpdatatables/source/class.wdtconfigcontroller.php

In this file, please search for this, there should be two occurrences, first one around line 82 as :

if (count($wpDataTable->getDataRows()) > 2000) {

And second one around line 143:

if (count($wpDataTable->getDataRows()) > 2000) {

That will increase the server-side processing option automatic limit.

We just advise caution not to increase that number 'too high' to avoid going over the limit what your Hosting Server's PHP Limitations can handle.

Usually, up to around 5 to 6 thousand rows should pose no significant performance issues, but if you go higher than that data size without server-side processing, you could experience slow loading times.

You can certainly test to see how a Table behaves on front-end, and if it loads too slow/or freezes the browser's Page, you can go back in the Table's Back-End and enable server-side processing for that Table.

3. To summarize :

If you need to have the brackets in table name - you can just disable server-side and have no filter/search issues;

or if you need server-side enabled - then you would have to rename the SQL Table and remove any brackets, or any symbol that throws an error by our Parser.

I realise that is not ideal - but at the moment, our SQL Parser has these limitations.

Let me know if that helps.