What would be a fix or migration for phpMyAdmin

问题:

I am working with large amounts of data and starting to get odd behavior when checking my data in phpMyAdmin. Row counts display ~ prefixes when count is high, supposedly estimates of the count. I will also get for example; 711 pages of data (x 30 rows), select the 711th page (last one) and then it will offer up more pages in the 800's, that are equal to none when selected.

This post describes the issue here but it does not offer a solution or potential instabilities. I have taken on perfecting my data types, keys and insertion process with little luck on understanding how to fix this or if there is any unseen deprecation of my data. The inserts and updates come from local PHP and off-server Python if that makes any difference.

回答1:

If you're using InnoDB tables, approximate counts are one of its "things", as described here. It has nothing really to do with phpMyAdmin. phpMyAdmin is just a frontend for the database and it relies on the data given by the database; if the database can only supply approximate counts quickly, then that's it.

And since phpMyAdmin is only a tool to simplify basic interactions with the database, I don't see the big issue. It shouldn't be your primary tool to browse through 800 pages of data to begin with. But, if you'd follow the hints provided by phpMyAdmin, you'd end up with a solution here.