(mysql.info.gz) Other-vendor column types

Info Catalog

(mysql.info.gz) Choosing types

(mysql.info.gz) Column types

 
 11.7 Using Column Types from Other Database Engines
 ===================================================
 
 To make it easier to use code written for SQL implementations from other
 vendors, MySQL maps column types as shown in the following table.  These
 mappings make it easier to import table definitions from other database
 engines into MySQL:
 
 *Other Vendor Type*       *MySQL Type*
 `BINARY(M)'               `CHAR(M) BINARY' (before MySQL 4.1.2)
 `CHAR VARYING(M)'         `VARCHAR(M)'
 `FLOAT4'                  `FLOAT'
 `FLOAT8'                  `DOUBLE'
 `INT1'                    `TINYINT'
 `INT2'                    `SMALLINT'
 `INT3'                    `MEDIUMINT'
 `INT4'                    `INT'
 `INT8'                    `BIGINT'
 `LONG VARBINARY'          `MEDIUMBLOB'
 `LONG VARCHAR'            `MEDIUMTEXT'
 `LONG'                    `MEDIUMTEXT' (MySQL 4.1.0 on)
 `MIDDLEINT'               `MEDIUMINT'
 `VARBINARY(M)'            `VARCHAR(M) BINARY' (before MySQL 4.1.2)
 
 As of MySQL 4.1.2, `BINARY' and `VARBINARY' are distinct data types and
 are not converted to `CHAR BINARY' and `VARCHAR BINARY'.
 
 Column type mapping occurs at table creation time, after which the
 original type specifications are discarded.  If you create a table with
 types used by other vendors and then issue a `DESCRIBE TBL_NAME'
 statement, MySQL reports the table structure using the equivalent MySQL
 types.
 

Info Catalog

(mysql.info.gz) Choosing types

(mysql.info.gz) Column types