Table with 3000 rows – worth it?
-
Hi Tobias,
Thanks so much for everything you do. I have a table with 3000 rows that I’d like to import from a CSV file. I was reading this thread, where you suggested a different solution for someone with 20,000 rows:
However, I’ll have to discourage you from trying this. 20,000 rows will not be fun. You might be able to successfully import this table, but you will then most probably not be able to edit it at all on the “Edit” screen, due to the large amount of textareas that the browser has to handle, and due to which your browser will be slow or even crash.
(If editing on the “Edit” screen is not a necessity, you might be able to use the trick from http://wordpress.org/support/topic/working-with-large-tables to hide the “Table Content” box, but that’s kind of ugly.)
Additionally, TablePress can only show the entire table on the frontend, which means that the entire data set has to be transmitted to the viewer every time, which can also be slow (depending on the amount of data in the table).Thus, a custom solution, based e.g. on a custom mySQL table that you run specific queries on with PHP should be a much better and more performant solution. Of course, you can still use the JS functions (sorting, search, …) on this by manually adding the DataTables JS library from http://www.datatables.net . All of this will require custom coding though…
My question is, would 3000 be worth doing? I don’t need to use the edit screen.
Would this still be too much data to transmit to the viewer?
Right now I’m getting the 500 internal server error just by trying to upload the file. I was reading about the memory issues. Just trying to decide if Tablepress is good for this or if a custom solution is the way to go.
Thanks!
James
The topic ‘Table with 3000 rows – worth it?’ is closed to new replies.