PDF (US Ltr)
- 41.8Mb
PDF (A4)
- 41.9Mb
Man Pages (TGZ)
- 272.4Kb
Man Pages (Zip)
- 378.3Kb
Info (Gzip)
- 4.2Mb
Info (Zip)
- 4.2Mb
Search Results
https://dev.mysql.com/doc/refman/9.7/en/integer-types.html
As an extension to the standard, MySQL also supports the integer types TINYINT, MEDIUMINT, and BIGINT. MySQL supports the SQL standard integer types INTEGER (or INT) and SMALLINT. The following table shows the required storage and range for each ...
https://dev.mysql.com/doc/refman/9.7/en/example-auto-increment.html
See Section 13.1.2, “Integer Types (Exact Value) - INTEGER, INT, SMALLINT, TINYINT, MEDIUMINT, BIGINT” for the ranges of all the integer types. You can also explicitly assign 0 to the column to generate sequence numbers, unless the ...
https://dev.mysql.com/doc/refman/9.7/en/srjs-data-arguments.html
The data types are listed here: Integer: All variants and aliases of MySQL integer data types are supported, including TINYINT, SMALLINT, MEDIUMINT, INT, and BIGINT. Most MySQL data types are supported for MLE stored program input and output ...
https://dev.mysql.com/doc/refman/9.7/en/storage-requirements.html
For example, in NDB tables, the TINYINT, SMALLINT, MEDIUMINT, and INTEGER (INT) column types each require 4 bytes storage per record due to the alignment factor. InnoDB Table Storage Requirements NDB Table Storage Requirements Numeric Type Storage ...
https://dev.mysql.com/doc/refman/9.7/en/data-size.html
MEDIUMINT is often a better choice than INT because a MEDIUMINT column uses 25% less space. Design your tables to minimize their space on the disk. This can result in huge improvements by reducing the amount of data written to and read from disk.
https://dev.mysql.com/doc/refman/9.7/en/other-vendor-data-types.html
To facilitate the use of code written for SQL implementations from other vendors, MySQL maps data types as shown in the following table. These mappings make it easier to import table definitions from other database systems into MySQL. If you create ...
https://dev.mysql.com/doc/refman/9.7/en/mysql-cluster-programs-ndb-restore.html
For example, data from a CHAR(20) column can be restored to a column declared as VARCHAR(20), VARCHAR(30), or CHAR(30); data from a MEDIUMINT column can be restored to a column of type INT or BIGINT. The NDB Cluster restoration program is ...
https://dev.mysql.com/doc/refman/9.7/en/keywords.html
Certain keywords, such as SELECT, DELETE, or BIGINT, are reserved and require special treatment for use as identifiers such as table and column names. This may also be true for the names of built-in functions. Some keywords which are otherwise ...
https://dev.mysql.com/doc/refman/9.7/en/srjs-session-info.html
mle_set_session_state() The MLE component provides this function as a means for determining the rules in effect during the current session for converting MySQL integer types (TINYINT, SMALLINT, MEDIUMINT, INT, BIGINT) and MySQL decimal types ... For ...
https://dev.mysql.com/doc/refman/9.7/en/replication-features-differing-tables.html
Supported conversions between different but similar data types are shown in the following list: Between any of the integer types TINYINT, SMALLINT, MEDIUMINT, INT, and BIGINT. Source and target tables for replication do not have to be identical. A ...