Data Type Conversion

The global sync variable data_conversion_compatibility_level controls the way certain data conversions are performed. This variable can have the following possible values: '6.0', '6.5', '7.0','7.5'. Higher values introduce stricter checking of values and will error for conversions that worked at lower levels. For example, the '7.0' level will fail the conversion of 'abc' to an integer value, while the '6.0' level will silently convert it to a NULL or 0.

The following table lists the data type conversion checks and behavior changes that are introduced with each data_conversion_compatibility_level value. Note that the data type conversion checks introduced in a compatibility level are preserved in subsequent levels.

data_conversion_compatibility_level	Data Type Conversion Checks
`6.0`	The lowest data type conversion compatibility level. Default value for SingleStore engine versions lower than 8.0.
`6.5`	Error on integer overflows and underflows in `INSERT` statements. This check applies to all `INTEGER` data types, including `BIGINT`, `INT`, `MEDIUMINT`, `SMALLINT`, `TINYINT`, `BIT`, and `BOOL`. Error on string inputs to `VARCHAR` columns that are too short to store the data. This check is run against `INSERT` statements. Error on string inputs to `LONGBLOB`, `MEDIUMBLOB`, `BLOB`, `TINYBLOB`, `LONGTEXT`, `MEDIUMTEXT`, `TEXT`, and `TINYTEXT` columns that are too short to store the data. This check is run against `INSERT` statements. Error on invalid string to int conversion in `INSERT` statements. Only strings with valid characters will be converted to integers.
`7.0`	Error on string inputs to `CHAR` columns that are too short to store the data. This check is run against `INSERT` statements. Error on inputs to `BINARY` columns that are too short to store the data. This check is run against `INSERT` statements. Error on decimal inputs that do not match the size specified in the `DECIMAL` column definition. This check is run against `INSERT` statements. Error on invalid or out-of-range date inputs to `DATE`, `DATETIME`, `DATETIME(6)`, and `YEAR` columns in `INSERT` statements. Errors on zero value date inputs into `DATE`, `DATETIME`, and `DATETIME(6)` columns in `INSERT` statements. Arithmetic operations involving `DATE` and `INT` values are performed by converting the `INT` data into intervals (days) instead of converting both data types to `DOUBLE`.
`7.5`	Error on invalid string to `DECIMAL` conversion in `INSERT` statements. Only strings with valid characters undergo numeric conversion.

It’s recommended to set the data_conversion_compatibility_level variable to the highest available value for new application development. For existing applications, it’s also recommended to use the highest available level, but it’s recommended that you test your application before deploying this change. In particular, changing the value of data_conversion_compatibility_level can change the behavior of expressions in computed columns.

If a computed column value changes due to a change in data_conversion_compatibility_level; columnstore sorting, indexes, and sharding can become logically corrupted. SingleStore does not recompile an existing plan when data_conversion_compatibility_level or sql_mode changes.

Note

sql_mode is persisted to the CREATE TABLE statement. Therefore, the computed column of a table always uses the sql_mode that the table is created with, which may be different from the current sql_mode.

Best Practices to Avoid Data Corruption

Review the computed column expressions when changing data_conversion_compatibility_level.
Perform application upgrade tests.

For example, if a computed column contains corrupted data and you have to switch to a higher data_conversion_compatibility_level, you may need to drop the computed column before changing the level. Once the level is increased, add the computed column to the table. Alternatively, if a persisted computed column is used in a columnstore key, you may have to create a new table and select data into this new table. After copying the data, drop the old table and rename the new table.

The following examples demonstrate how the behavior of expressions may change if data_conversion_compatibility_level is changed.

Example 1

SQL

SET GLOBAL data_conversion_compatibility_level = '6.0';

SQL

SELECT DATE('2019-04-20') + 2;

+------------------------+
| DATE('2019-04-20') + 2 |
+------------------------+
|               20190422 |
+------------------------+

Example 2

SQL

SET GLOBAL data_conversion_compatibility_level = '7.0';

SQL

SELECT DATE('2019-04-20') + 2;

+------------------------+
| DATE('2019-04-20') + 2 |
+------------------------+
| 2019-04-22             |
+------------------------+

The following example shows the error message generated if a zero value is attempted to be inserted into a DATE, DATETIME, or DATETIME(6) column if the data_conversion_compatibility_level is set to 7.0 or higher.

SQL

SET GLOBAL data_conversion_compatibility_level = '7.0';

SQL

CREATE TABLE dates (dt DATETIME);
INSERT INTO dates VALUES ('0000-00-00');

ERROR 2363 (HY000): Leaf Error: Invalid DATE/TIME in type conversion

See the table on the Time and Date page for examples of zero values for DATE, DATETIME, and DATETIME(6) data types. This page also discusses how date (and time) values are implicitly converted from string literals (e.g., '2023-02-03') and how to use date and time functions to perform explicit conversions from string literals.

Data Type Conversion

On this page

Best Practices to Avoid Data Corruption

Was this article helpful?

On this page

Was this article helpful?