MySQL :: MySQL 8.0 Reference Manual

Search Results

Displaying 11 to 20 of 20 total results

« Previous
1
2
Next »

https://dev.mysql.com/doc/refman/8.0/en/numeric-type-syntax.html

For integer data types, M indicates the minimum display width. Display width is unrelated to the range of values a type can store, as described in Section 13.1.6, “Numeric Type Attributes”. For floating-point and fixed-point data types, M is ...

1.3 What Is New in MySQL 8.0

https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html

Such implicit casts are now performed between temporal types (DATE, DATETIME, TIMESTAMP, TIME) and numeric types (SMALLINT, TINYINT, MEDIUMINT, INT/INTEGER, BIGINT; DECIMAL/NUMERIC; FLOAT, DOUBLE, REAL; BIT) whenever they are compared using any of ... This section summarizes what has been added to, deprecated in, and removed from MySQL ...

15.2.9 LOAD DATA Statement

https://dev.mysql.com/doc/refman/8.0/en/load-data.html

For TINYINT, SMALLINT, MEDIUMINT, INT, and BIGINT, the field widths are 4, 6, 8, 11, and 20, respectively, no matter what the declared display width is. The file can be read from the server host or the client host, depending on whether the LOCAL ...

11.3 Keywords and Reserved Words

https://dev.mysql.com/doc/refman/8.0/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 ...

14.17.5 Functions That Return JSON Value Attributes

https://dev.mysql.com/doc/refman/8.0/en/json-attribute-functions.html

The functions in this section return attributes of JSON values. An error occurs if the argument is not a valid JSON document. An empty array, empty object, or scalar value has depth 1. A nonempty array containing only elements of depth 1 or ...

17.21.4 Troubleshooting InnoDB Data Dictionary Operations

https://dev.mysql.com/doc/refman/8.0/en/innodb-troubleshooting-datadict.html

Information about table definitions is stored in the InnoDB data dictionary. If you move data files around, dictionary data can become inconsistent. If a data dictionary corruption or consistency issue prevents you from starting InnoDB, see Section ...

14.5 Flow Control Functions

https://dev.mysql.com/doc/refman/8.0/en/flow-control-functions.html

Otherwise, the result is an integer type (with one exception): If all integer types are all signed or all unsigned, the result is the same sign and the precision is the highest of all specified integer types (that is, TINYINT, SMALLINT, MEDIUMINT, ...The second syntax returns the result for the first condition that is ...

5.6.9 Using AUTO_INCREMENT

https://dev.mysql.com/doc/refman/8.0/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 ...

13.3.5 The ENUM Type

https://dev.mysql.com/doc/refman/8.0/en/enum.html

An ENUM is a string object with a value chosen from a list of permitted values that are enumerated explicitly in the column specification at table creation time. See Section 13.3.1, “String Data Type Syntax” for ENUM type syntax and length ...

17.6.1.5 Converting Tables from MyISAM to InnoDB

https://dev.mysql.com/doc/refman/8.0/en/converting-tables-to-innodb.html

For the ranges of the different integer types, see Section 13.1.2, “Integer Types (Exact Value) - INTEGER, INT, SMALLINT, TINYINT, MEDIUMINT, BIGINT”. If you have MyISAM tables that you want to convert to InnoDB for better reliability and ...

Displaying 11 to 20 of 20 total results

« Previous
1
2
Next »