1 of 1

ColumnStore Data Types

Reference for MariaDB ColumnStore data types: numeric (BOOLEAN, integers, DECIMAL, FLOAT/DOUBLE), variable-length string types, and standard MariaDB date and time types.

ColumnStore supports the following data types:

Numeric Data Types

Datatypes

Column Size

Description

String Data Types

Datatypes

Column Size

Description

Date and Time Data Types

Datatypes

Column Size

Description

Notes

ColumnStore treats a zero-length string as a NULL value.
As with core MariaDB, ColumnStore employs “saturation semantics” on integer values. This means that if a value is inserted into an integer field that is too big/small for it to hold (i.e., it is more negative or more positive than the values indicated above), ColumnStore will “saturate” that value to the min/max value indicated above as appropriate. For example, for a SMALLINT column, if 32800 is attempted, the actual value inserted will be 32767.

ColumnStore Data Types

Reference for MariaDB ColumnStore data types: numeric (BOOLEAN, integers, DECIMAL, FLOAT/DOUBLE), variable-length string types, and standard MariaDB date and time types.

ColumnStore supports the following data types:

Numeric Data Types

Datatypes

Column Size

Description

String Data Types

Datatypes

Column Size

Description

Date and Time Data Types

Datatypes

Column Size

Description

Notes

ColumnStore treats a zero-length string as a NULL value.
As with core MariaDB, ColumnStore employs “saturation semantics” on integer values. This means that if a value is inserted into an integer field that is too big/small for it to hold (i.e., it is more negative or more positive than the values indicated above), ColumnStore will “saturate” that value to the min/max value indicated above as appropriate. For example, for a SMALLINT column, if 32800 is attempted, the actual value inserted will be 32767.

2, 4, or 8 bytes

A packed fixed-point number that can have a specific total number of digits and with a set number of digits after a decimal. The maximum precision (total number of digits) that can be specified is 18.

4 bytes

Stored in 32-bit IEEE-754 floating point format. As such, the number of significant digits is about 6and the range of values is approximately +/- 1e38.The MySQL extension to specify precision and scale is not supported.

8 bytes

Stored in 64-bit IEEE-754 floating point format. As such, the number of significant digits is about 15 and the range of values is approximately +/-1e308. The MySQL extension to specify precision and scale is not supported. “REAL” is a synonym for “DOUBLE”.

4-bytes

Values are stored as the number of seconds since 1970-01-01 00:00:00 UTC, and optionally microseconds. The max value is currently 2038-01-19 03:14:07 UTC. Supported starting with MariaDB ColumnStore 1.4.2.

ColumnStore's largest negative and positive numbers appear to be 2 less than what MariaDB supports. ColumnStore reserves these for its internal use, and they cannot be used. For example, if there is a need to store -128 in a column, the TINYINT datatype cannot be used; the SMALLINT datatype must be used instead. If the value -128 is inserted into a TINYINT column, ColumnStore will saturate it to -126 (and issue a warning).

ColumnStore truncates rather than rounds decimal constants that have too many digits after the decimal point during bulk load and when running SELECT statements. For INSERT and UPDATE, however, the MariaDB parser will round such constants. You should verify that the ETL tools used and any INSERT/UPDATE statements only specify the correct number of decimal digits to avoid potential confusion.

An optional display width may be added to the BIGINT, INTEGER/INT, SMALLINT & TINYINT columns. As with core MariaDB tables, this value does not affect the internal storage requirements of the column, nor does it affect the valid value ranges.

All columns in ColumnStore are nullable, and the default value for any column is NULL. You may optionally specify NOT NULL for any column and/or one with a DEFAULT value.

Unlike other MariaDB storage engines, the actual storage limit for LONGBLOB/LONGTEXT is 2,100,000,000 bytes instead of 4 GB per entry. MariaDB's client API is limited to a row length of 1 GB.

ColumnStore Data Types

hashtagNumeric Data Types

hashtagString Data Types

hashtagDate and Time Data Types

hashtagNotes

ColumnStore Data Types

hashtagNumeric Data Types

hashtagString Data Types

hashtagDate and Time Data Types

hashtagNotes

Numeric Data Types

String Data Types

Date and Time Data Types

Notes

Numeric Data Types

String Data Types

Date and Time Data Types

Notes