什么是phpMyAdmin的20,000行限制的修复或迁移，真的不稳定吗? [英] What would be a fix or migration for phpMyAdmin's 20,000 row limitation and is anything really unstable?

问题描述

我正在处理大量数据，并且在phpMyAdmin中检查数据时开始出现奇怪的行为.当计数很高时，行计数显示~前缀(据推测是计数的估计值).我也会举个例子. 711页数据(x 30行)，选择第711页(最后一页)，然后它将提供800页中的更多页，这些页在被选择时等于无.

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.

这篇文章此处描述了问题，但是它没有提供解决方案或潜在的不稳定因素.我已经很完善我的数据类型，键和插入过程，几乎不了解如何解决这个问题，或者是否有我的数据过时的地方.如果有任何区别，则插入和更新来自本地PHP和脱机Python.

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.

推荐答案

如果您使用的是InnoDB表，则近似计数是其事物"之一，如

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.

并且由于phpMyAdmin只是简化与数据库的基本交互的工具，因此我认为没有什么大的问题.首先，它不应该是浏览800页数据的主要工具.但是，如果您遵循phpMyAdmin提供的提示，则会得到一个解决方案此处.

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.

这篇关于什么是phpMyAdmin的20,000行限制的修复或迁移，真的不稳定吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！