The following table provides a short overview of ClickHouse data types compared to MySQL data types:
| ClickHouse | MySQL | Comment |
| UInt8, UInt16, UInt32, UInt64 | TINYINT UNSIGNED, SMALLINT UNSIGNED, INT UNSIGNED, BIGINT UNSIGNED | |
| Int8, Int16, Int32, Int64 | TINYINT SIGNED, SMALLINT SIGNED, INT SIGNED, BIGINT SIGNED | |
| Float32, Float64 | FLOAT, DOUBLE | Supports inf, -inf, nan, recommended NOT to use by ClickHouse! |
| String | BLOB, TEXT, VARCHAR, VARBINARY | No encoding. Recommended to use UTF-8. In fact behaves like a BLOB. |
| FixedString(n) | CHAR, BINARY | \0 padded. Less functions available than String, in fact it behaves like BINARY. |
| Date | DATE | UNIX epoch date up to 2038. |
| DateTime | DATETIME, TIMESTAMP | UNIX epoch timestamp up to 2038. |
| Enum | ENUM | Similar to MySQL ENUM. Behaves like Int8/16. |
| Array(type) | n.a. | Array of type. Closest equivalent in MySQL is JSON? Not well supported. |
| Tuple() | n.a. | |
| Nested() | n.a. | Closest equivalent in MySQL is JSON? |
| AggregateFunction() | n.a. | |
| Set | n.a. | |
| Expression | n.a. |