Instead, it converts boolean values into integer data types (TINYINT).

This is unavoidable because of the way FLOAT is implemented, and it affects every programming language. MySQL does not have a boolean (or bool) data type. It's an inexact numeric type, and it will have rounding errors. Or you could use FLOAT with no arguments, and it will not constrain the number of digits at all. For example, the value 1196.104 could be inserted to FLOAT(11,7) or FLOAT(10,6). If you want to store larger values, declare FLOAT with enough digits to hold the values you use. | Warning | 1264 | Out of range value for column 'f' at row 1 | Query OK, 1 row affected, 1 warning (0.02 sec) In other words, you gave it the constraint to max out at 1000.0000000, because you told it to max out at 10 digits, of which 7 digits are to the right of the decimal point. Here, (M,D) means than values can be stored with up to M digits in total, of which D digits may be after the decimal point. MySQL permits a nonstandard syntax: FLOAT(M,D) or REAL(M,D) or DOUBLE PRECISION(M,D). For more information about floating-point comparisons, see Section B.3.4.8, Problems with Floating-Point Values. MySQL FORMAT () formats a number in the format- ‘. To format your numerical output in MySQL, we use the FORMAT () function.

When you give a value that won't fit in the number of digits, it caps the value and uses the greatest value that can fit. One way to avoid such problems is to use CAST() so that a value is not converted implicitly to a float-point number: mysql> SELECT CAST9223372036854775807 AS UNSIGNED) 9223372036854775806 -> 0. You must have observed so far that when you output a numerical value in MySQL, it does not return the number with formatting. This is working exactly as intended by the FLOAT(10,7).

Mysql float