Comment 1 for bug 1570583

this is because the validation for this only checks a min value and not a max value. Any max value is allowed and it passes to the database for insertion. The database has a 32-bit int type for the column, so large numbers will fail.

The correct solution to this is to just modify the validation to the API to check a max value. The database should column type should not be changed.