title: What would be a fix or migration for phpMyAdmin's 20,000 row limitation and is anything really unstable?
body: <p>I am working with large amounts of data and starting to get odd behavior when checking my data in phpMyAdmin. Row counts display <code>~</code> 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. </p>
  
  <p>This post describes the issue <a href="https://stackoverflow.com/questions/4205062/phpmyadmin-showing-negative-total-records-for-a-database-table">here</a> 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.</p>