I am trying to create a table based on a CSV file stored in my FTP (same domain). If I enter the URL for the location of the CSV file, wpdatatable doens't recognize it's there. But when I upload the CSV into the media folder (/wp-content/uploads/), it does.
But I don't want wpdatatable to read from a folder that also contains hundreds of image files. Is there a way for wpdatatable to read from a different folder?
The other question is, is it faster to load a table linked to a CSV file in my server OR linked to a table in an SQL server? I'd like to go with whiever is even slightly faster.
It can be any folder on the server, but you can't pass the URL. It needs to be the full path. So, on a localhost it would be /var/www/html/site_name/.......
When your data set is larger than a couple of thousand rows, it can’t effectively be loaded in the page. It first reads the data from the source, and then prints out the complete table data on your page; so, as the row count grows, it makes both the page generation time on server side and the page load and initialization time on client side, slower and slower. If your host has a certain memory or timeout limit defined for PHP scripts, it can ‘break’ the page, because the script would try to allocate more memory than it’s allowed.
Hi,
I am trying to create a table based on a CSV file stored in my FTP (same domain). If I enter the URL for the location of the CSV file, wpdatatable doens't recognize it's there. But when I upload the CSV into the media folder (/wp-content/uploads/), it does.
But I don't want wpdatatable to read from a folder that also contains hundreds of image files. Is there a way for wpdatatable to read from a different folder?
The other question is, is it faster to load a table linked to a CSV file in my server OR linked to a table in an SQL server? I'd like to go with whiever is even slightly faster.
Thank you.
Hi IW
Thank you for reaching out to us.
It can be any folder on the server, but you can't pass the URL. It needs to be the full path. So, on a localhost it would be /var/www/html/site_name/.......
When your data set is larger than a couple of thousand rows, it can’t effectively be loaded in the page. It first reads the data from the source, and then prints out the complete table data on your page; so, as the row count grows, it makes both the page generation time on server side and the page load and initialization time on client side, slower and slower. If your host has a certain memory or timeout limit defined for PHP scripts, it can ‘break’ the page, because the script would try to allocate more memory than it’s allowed.
So if your table is large, it is much better to port it to MySQL table (you can use “Create a table by importing data from data source” to import your CSV file to MySQL).
thanks for your reply. Yeah it seems smaller tables are better with csvs and bigger ones are better off with MYSQL. cheers
You are most welcome
If there is anything else we can assist you with please don't hesitate to open a new ticket.
Have a wonderful day!