MySQL and MariaDB - Starter Kit

Mapping

Mapping

The following table explains how the MySQL datatypes are mapped to the target databases.

MySQL Datatype	Firebolt Datatype	Snowflake Datatype
Numbers
`TINYINT`	`INTEGER`	`TINYINT`
`SMALLINT`	`INTEGER`	`SMALLINT`
`MEDIUMINT`	`INTEGER`	`INT`
`INT`	`INTEGER`	`INT`
`BIGINT`	`BIGINT`	`BIGINT`
`NUMERIC`	`NUMERIC`	`NUMBER`
`DECIMAL`	`NUMERIC`	`NUMBER`
`FLOAT`	`REAL`	`FLOAT`
`DOUBLE`	`DOUBLE`	`FLOAT`
`REAL`	`DOUBLE`	`FLOAT`
`BIT`	`INTEGER`	`BOOLEAN`
`BOOL`	`BOOLEAN`	`BOOLEAN`
`BOOLEAN`	`BOOLEAN`	`BOOLEAN`
`YEAR`	`INTEGER`	`NUMBER`
Times
`DATE`	`DATE`	`DATE`
`DATETIME`	`TIMESTAMP`	`TIMESTAMP_NTZ`
`TIMESTAMP`	`TIMESTAMP`	`TIMESTAMP_LTZ`
`TIME`	`TEXT`	`TIME`
Strings
`CHAR`	`TEXT`	`VARCHAR`
`VARCHAR`	`TEXT`	`VARCHAR`
`TINYTEXT`	`TEXT`	`VARCHAR`
`TEXT`	`TEXT`	`VARCHAR`
`MEDIUMTEXT`	`TEXT`	`VARCHAR`
`LONGTEXT`	`TEXT`	`VARCHAR`
`JSON`	`TEXT`	`VARIANT`
`POINT`	`TEXT`	`VARCHAR`
`LINESTRING`	`TEXT`	`VARCHAR`
`POLYGON`	`TEXT`	`VARCHAR`
`GEOMETRY`	`TEXT`	`VARCHAR`
`MULTIPOINT`	`TEXT`	`VARCHAR`
Blobs
`BINARY`	`BYTEA`	`BINARY`
`VARBINARY`	`BYTEA`	`BINARY`
`TINYBLOB`	`BYTEA`	`BINARY`
`BLOB`	`BYTEA`	`BINARY`
`MEDIUMBLOB`	`BYTEA`	`BINARY`
`LONGBLOB`	`BYTEA`	`BINARY`
Sets
`ENUM`	`TEXT`	`VARCHAR`
`SET`	`TEXT`	`VARCHAR`

Implementation PostgreSQL

⌘I