Editing large tables

My solution to the large table issue is to export the table (HTML exporting with UTF-8 or UTF-16 coding works best for me). I then import the entire table into a FileMaker database, where I now do the maintenance — effortless, fast, painless. I then periodically export the complete database (again, HTML / UTF-8) and re-import it into TablePress, replacing the existing database with every import. OK, the refresh after the import is still painfully slow, and it seems to take ages until I can update the “last modified” entry in the comment to the table — but at least, I can avoid any editing other than in the comment. The same would work with MS Excel, I’m sure — though I really prefer a database over a spreadsheet. I only edit small tables in the TablePress GUI directly.
On the bright side: Tobias fixed one sticky speed issue (thanks a lot! Or was this a WP update that had this effect?): always the first “Save” in a TablePress session used to take forever, no matter how big or small the database was. With the latest update(s) (1.8.1?), this issue is entirely gone.

Best wishes,
Rolf

Hi Tobias,

Whatever fixed it — the saving issue is gone. It must have been WP, as that’s the only thing that changed, apart from the occasional plugin updates. I haven’t changed browser. The issue with large tables is linked to the browser (Chrome in my case) loading the entire table into the buffer. But also subsequent changes in the width of individual columns, etc. are incredibly slow, hence I really prefer external editing with any table with more than, say, 100 – 200 records.

Best wishes,
Rolf

Hi there,

let me just throw in my 2c worth of advice, partly doubling up on what I stated above. As mentioned, some of my tables are large (1300 & more records, up to 10 fields), and right now, editing in the admin GUI is so slow, clumsy and unhandy that I concluded that simple amendments / speedup fixes etc. won’t do: the editing GUI needs a serious rework / redesign for editing large tables becomes usable. Understandably, this is not going to happen in a matter of weeks, even months.
So, for most of my tables (except very small ones) I now export into CSV, then import into an external, local utility (Filemaker in my case, but MS Excel should work as well). From then on, I do all editing in that external utility. I never re-import from TP again, but just periodically export (UTF-8 into HTML works best for me), and then reimport those updates (the full table, every table, replacing the old one) into TablePress. Filemaker fills empty cells with “<br/>” — but that is OK with me (TP is fine with that, too).
I noted that even just importing a large table can be painfully slow, because apparently the browser needs to load the entire table before it can display any contents, and (for example) further mods in the header info (which are not touched by the import) are possible. The current version of Chrome behaves much better in that respect than older ones, but it still may be painful. So, before importing a large table, I open any other table, make sure the “Content” tab/segment is closed, then select “Import” -> select the local file to import, select the target table (replacing entire content), then import. The import still takes a few seconds (my upload is about 0.5 MB), and editing the header takes another few seconds, but nowhere near what it used to be. Just don’t open the “Content” tab for this table, but open a small table before re-opening the tab.
It’s a livable situation for me (and I simply don’t know of any alternative to TablePress anyway!).

Best wishes,
Rolf