When an operator is used with operands of different types, type conversion occurs to make the operands compatible. Some conversions occur implicitly. For example, MySQL automatically converts strings to numbers as necessary, and vice versa.
mysql> SELECT 1+'1'; -> 2 mysql> SELECT CONCAT(2,' test'); -> '2 test'
mysql> SELECT 38.8, CAST(38.8 AS CHAR); -> 38.8, '38.8' mysql> SELECT 38.8, CONCAT(38.8); -> 38.8, '38.8'
See later in this section for information about the character set
of implicit number-to-string conversions, and for modified rules
that apply to
CREATE TABLE ... SELECT
The following rules describe how conversion occurs for comparison operations:
If one or both arguments are
NULL, the result of the comparison is
NULL, except for the
<=>equality comparison operator. For
NULL <=> NULL, the result is true. No conversion is needed.
If both arguments in a comparison operation are strings, they are compared as strings.
If both arguments are integers, they are compared as integers.
Hexadecimal values are treated as binary strings if not compared to a number.
If one of the arguments is a
DATETIMEcolumn and the other argument is a constant, the constant is converted to a timestamp before the comparison is performed. This is done to be more ODBC-friendly. This is not done for the arguments to
IN(). To be safe, always use complete datetime, date, or time strings when doing comparisons. For example, to achieve best results when using
BETWEENwith date or time values, use
CAST()to explicitly convert the values to the desired data type.
A single-row subquery from a table or tables is not considered a constant. For example, if a subquery returns an integer to be compared to a
DATETIMEvalue, the comparison is done as two integers. The integer is not converted to a temporal value. To compare the operands as
CAST()to explicitly convert the subquery value to
If one of the arguments is a decimal value, comparison depends on the other argument. The arguments are compared as decimal values if the other argument is a decimal or integer value, or as floating-point values if the other argument is a floating-point value.
In all other cases, the arguments are compared as floating-point (double-precision) numbers. For example, a comparison of string and numeric operands takes place as a comparison of floating-point numbers.
For information about conversion of values from one temporal type to another, see Section 11.2.7, “Conversion Between Date and Time Types”.
Comparison of JSON values takes place at two levels. The first level of comparison is based on the JSON types of the compared values. If the types differ, the comparison result is determined solely by which type has higher precedence. If the two values have the same JSON type, a second level of comparison occurs using type-specific rules. For comparison of JSON and non-JSON values, the non-JSON value is converted to JSON and the values compared as JSON values. For details, see Comparison and Ordering of JSON Values.
The following examples illustrate conversion of strings to numbers for comparison operations:
mysql> SELECT 1 > '6x'; -> 0 mysql> SELECT 7 > '6x'; -> 1 mysql> SELECT 0 > 'x6'; -> 0 mysql> SELECT 0 = 'x6'; -> 1
For comparisons of a string column with a number, MySQL cannot use
an index on the column to look up the value quickly. If
str_col is an indexed string column,
the index cannot be used when performing the lookup in the
SELECT * FROM tbl_name WHERE str_col=1;
The reason for this is that there are many different strings that
may convert to the value
1, such as
' 1', or
Comparisons between floating-point numbers and large values of
INTEGER type are approximate because the
integer is converted to double-precision floating point before
comparison, which is not capable of representing all 64-bit
integers exactly. For example, the integer value
253 + 1 is not representable as a
float, and is rounded to 253 or
253 + 2 before a float comparison,
depending on the platform.
To illustrate, only the first of the following comparisons compares equal values, but both comparisons return true (1):
mysql> SELECT '9223372036854775807' = 9223372036854775807; -> 1 mysql> SELECT '9223372036854775807' = 9223372036854775806; -> 1
When conversions from string to floating-point and from integer to
floating-point occur, they do not necessarily occur the same way.
The integer may be converted to floating-point by the CPU, whereas
the string is converted digit by digit in an operation that
involves floating-point multiplications. Also, results can be
affected by factors such as computer architecture or the compiler
version or optimization level. One way to avoid such problems is
CAST() so that a value is
not converted implicitly to a float-point number:
mysql> SELECT CAST('9223372036854775807' AS UNSIGNED) = 9223372036854775806; -> 0
For more information about floating-point comparisons, see Section B.3.4.8, “Problems with Floating-Point Values”.
Consistent conversion results across platforms, which eliminates, for example, Unix versus Windows conversion differences.
Accurate representation of values in cases where results previously did not provide sufficient precision, such as for values close to IEEE limits.
Conversion of numbers to string format with the best possible precision. The precision of
dtoais always the same or better than that of the standard C library functions.
Because the conversions produced by this library differ in some
cases from non-
dtoa results, the potential
exists for incompatibilities in applications that rely on previous
results. For example, applications that depend on a specific exact
result from previous conversions might need adjustment to
accommodate additional precision.
dtoa library provides conversions with the
D represents a
value with a
DECIMAL or string
F represents a
floating-point number in native binary (IEEE) format.
Dconversion is done with the best possible precision, returning
Das the shortest string that yields
Fwhen read back in and rounded to the nearest value in native binary format as specified by IEEE.
Fconversion is done such that
Fis the nearest native binary number to the input decimal string
These properties imply that
conversions are lossless unless
NaN. The latter values are not supported
because the SQL standard defines them as invalid values for
conversions, a sufficient condition for losslessness is that
D uses 15 or fewer digits of precision,
is not a denormal value,
NaN. In some cases,
the conversion is lossless even if
has more than 15 digits of precision, but this is not always the
Implicit conversion of a numeric or temporal value to string
produces a value that has a character set and collation determined
variables. (These variables commonly are set with
SET NAMES. For information about
connection character sets, see
Section 10.4, “Connection Character Sets and Collations”.)
This means that such a conversion results in a character
(nonbinary) string (a
LONGTEXT value), except in the case
that the connection character set is set to
binary. In that case, the conversion result is
a binary string (a
For integer expressions, the preceding remarks about expression evaluation apply somewhat differently for expression assignment; for example, in a statement such as this:
CREATE TABLE t SELECT integer_expr;
In this case, the table in the column resulting from the
expression has type
BIGINT depending on the length of
the integer expression. If the maximum length of the expression
does not fit in an
BIGINT is used instead. The length
is taken from the
max_length value of the
SELECT result set metadata (see
C API Basic Data Structures). This means that you can
BIGINT rather than
INT by use of a sufficiently long
CREATE TABLE t SELECT 000000000000000000000;