I was quite happy with this when I had a few tables on a site, say less than 10. But when you have many it gets very challenging remembering which is which.
You cannot filter or reorder them in the backend, you can give them a new ID that is not number-based so that you could at least make sense of them in human-readable form but the ID column is very narrow and does not expand.. so that is not such a good option either (you have to have a very sort basic naming convention and that does not even fit).
It is not WPML-compliant, so you have to make all of your various languages tables in the same backend page which can add yet another level of complexity: imagine having 4 languages with 30 some tables you end up with 120 un-reorderable tables.
You can not put tables in the trash to say.. help keeping them out of sight for a bit while you do some cleaning up.. you can only delete them.
You can not do any sort of “Quick Edit” as you can with posts, CPT’s etc.
All in all as with many many tools, heavy use exposes shortcomings. The responsiveness leaves a lot to be desired. A tool that felt great for fairly light use becomes cumbersome when put under strain. And a lot of the time it is the backend experience that is where things get fishy.
I’m trying to find a good (and short..) naming convention and adding a description for each. I wish the dev would at least make the ID column automatically expand to accommodate the characters.
Also my tables are fairly simple in and of themselves, but I could see how challenging it would be to work with massive ones with a lot of content.
This could be improved so much, I’d even pay for some sort of lifetime license if the things listed above were implemented (I had paid a little support money on this way back).
- The topic ‘Hard to work with when you have many tables’ is closed to new replies.