A2 Hosting Forums

Full Version: MySQL 4.x migration INT datatype issues
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
If you are on an older mysql server (a2s1-4), there was a glitch in mysql on the 32 bit tree for a while that was alllowing INT datatypes to creep beyond their allowed settings.

This may result in an overflow on a newer server where an INT datatype gets pinned to "2147483647" upon insertion. If this occurs, please adjust the database to the BIGINT type. This can be done in phpmyadmin, from the mysql client, or many third party clients.
Reference URL's