Data Types for MySQL
Data Type Definition
Keyword 1
|
|
|
|
|
|
|
Large signed, exact
whole number.
|
|
|
|
|
Fixed-length binary
string.
|
|
|
|
|
Varying-length binary
large object string.
|
|
|
|
|
Fixed-length character
string.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Signed, fixed-point
decimal number.
|
|
|
|
|
Signed, double precision,
floating-point number.
|
|
|
|
|
Character values from
a list of allowed values.
|
|
|
|
|
Signed, single precision
or double precision, floating-point number.
|
|
|
|
|
Regular signed, exact
whole number.
|
|
|
|
|
Varying-length binary
data.
|
|
|
|
|
Varying-length character
string.
|
|
|
|
|
Varying-length binary
data.
|
|
|
|
|
Regular signed, exact
whole number.
|
|
|
|
|
Varying-length character
string.
|
|
|
|
|
Character values from
a list of allowed values.
|
|
|
|
|
Small signed, exact
whole number.
|
|
|
|
|
Varying-length text
data.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Varying-length binary
large object string.
|
|
|
|
|
Very small signed, exact
whole number.
|
|
|
|
|
Varying-length text
data.
|
|
|
|
|
Varying-length character
string.
|
|
| 1The CT_PRESERVE= connection
argument, which controls how data types are mapped, can affect whether
a data type can be defined. The values FORCE (default) and FORCE_COL_SIZE
do not affect whether a data type can be defined. The values STRICT
and SAFE can result in an error if the requested data type is not
native to the data source, or the specified precision or scale is
not within the data source range.
|
| 2The MySQL data type cannot
be defined, and when data is retrieved, the native data type is mapped
to a similar data type.
|