PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 296.6Kb
Man Pages (Zip)
- 402.0Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/precision-math-numbers.html
Approximate-value data types and numeric literals are handled as floating-point numbers. For example, 2.34 is an exact-value (fixed-point) number, whereas 2.34E0 is an approximate-value (floating-point) number. The FLOAT and DOUBLE data types are ...
https://dev.mysql.com/doc/refman/8.0/en/no-matching-rows.html
If you are comparing FLOAT or DOUBLE columns with numbers that have decimals, you cannot use equality (=) comparisons. This problem is common in most computer languages because not all floating-point values can be stored with exact precision. In ...
https://dev.mysql.com/doc/refman/8.0/en/numeric-type-attributes.html
As of MySQL 8.0.17, the UNSIGNED attribute is deprecated for columns of type FLOAT, DOUBLE, and DECIMAL (and any synonyms) and you should expect support for it to be removed in a future version of MySQL. As of MySQL 8.0.17, AUTO_INCREMENT support is ... MySQL supports an extension for optionally specifying the display width of integer data types in parentheses following the base keyword for the ...
https://dev.mysql.com/doc/refman/8.0/en/create-table.html
Using AUTO_INCREMENT with FLOAT or DOUBLE columns is deprecated as of MySQL 8.0.17; expect support for it to be removed in a future version of MySQL. AUTO_INCREMENT An integer or floating-point column can have the additional attribute AUTO_INCREMENT. Columns using BLOB, TEXT, SET, ENUM, BIT, or spatial data types are not permitted; columns that use floating-point number types are also not ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-migration.html
InnoDB data and log files are binary-compatible on all platforms having the same floating-point number format. If the floating-point formats differ but you have not used FLOAT or DOUBLE data types in your tables, then the procedure is the same: ...
https://dev.mysql.com/doc/refman/8.0/en/constant-folding-optimization.html
row *************************** Level: Note Code: 1003 Message: /* select#1 */ select `test`.`t`.`ti` AS `ti` from `test`.`t` where (`test`.`t`.`ti` = 255) 1 row in set (0.00 sec) Floating- or fixed-point value. If the constant is one of the decimal ... Comparisons between constants and column values in which the constant value is out of range or of the wrong type with respect to the column type are now handled once during query optimization rather row-by-row than during ...
https://dev.mysql.com/doc/refman/8.0/en/spatial-convenience-functions.html
The functions in this section provide convenience operations on geometry values. Unless otherwise specified, functions in this section handle their geometry arguments as follows: If any argument is NULL, the return value is NULL. If any geometry ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-differing-tables.html
Between any of the decimal types DECIMAL, FLOAT, DOUBLE, and NUMERIC. FLOAT to DOUBLE is a non-lossy conversion; DOUBLE to FLOAT can only be handled lossily. Source and target tables for replication do not have to be identical. A table on the ...
https://dev.mysql.com/doc/refman/8.0/en/window-function-optimization.html
For example, adding a very small floating-point value to a very large value causes the very small value to be “hidden” by the large value. Loss of precision due to inverse aggregation is a factor only for operations on floating-point ... Window ...
https://dev.mysql.com/doc/refman/8.0/en/replication-rbr-safe-unsafe.html
In addition, statements using results from floating-point math functions—which are hardware-dependent—are always considered unsafe (see Section 19.5.1.12, “Replication and Floating-Point Values”). The “safeness” of a statement in MySQL ...