| Value range |
The value can be any combination of the following:
- ANSI_QUOTES: Treats string quote characters (double quotes „) as identifier quote characters (backticks `), so double quotes cannot be used to reference strings.
- ERROR_FOR_DIVISION_BY_ZERO: Generates an error when zero division occurs for data during INSERT or UPDATE statements.
- When ERROR_FOR_DIVISION_BY_ZERO mode is not enabled, dividing by zero returns NULL.
- When ERROR_FOR_DIVISION_BY_ZERO mode is enabled but strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES) is not enabled, dividing by zero returns NULL.
- When both strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES) and ERROR_FOR_DIVISION_BY_ZERO mode are enabled, dividing by zero is not allowed and generates an error.
- When both strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES) and ERROR_FOR_DIVISION_BY_ZERO mode are enabled and ignore is specified, dividing by zero returns NULL.
- HIGH_NOT_PRECEDENCE: The precedence of the NOT operator causes expressions such as
NOT a BETWEEN b AND c to be parsed as NOT(a BETWEEN b AND c).
- IGNORE_SPACE: Allows spaces between function names and characters. This field is currently only for compatibility; it can be set but has no effect.
- NO_AUTO_CREATE_USER: Does not allow creating users with empty passwords using the GRANT statement.
- NO_DIR_IN_CREATE: Ignores all INDEX DIRECTORY and DATA DIRECTORY directives when creating a table. This field is currently only for compatibility; it can be set but has no effect, and its behavior in OceanBase AI Database differs from MySQL.
- NO_ENGINE_SUBSTITUTION: Generates an error if the storage engine being used is disabled or not compiled. If this value is not set, the default storage engine is used as a substitute and an exception is thrown. This field is currently only for compatibility; it can be set but has no effect, and its behavior in OceanBase AI Database differs from MySQL.
- NO_FIELD_OPTIONS: Cannot print MySQL-specific column options in the output of
SHOW CREATE TABLE.
- NO_KEY_OPTIONS: Cannot print MySQL-specific index options in the output of
SHOW CREATE TABLE.
- NO_TABLE_OPTIONS: Cannot print MySQL-specific table options (such as ENGINE) in the output of
SHOW CREATE TABLE.
- NOUnsigned_SUBTRACTION: By default, subtraction between integer values (where one is of the UNSIGNED type) produces an unsigned result.
- NO_ZERO_DATE: Whether dates in the '0000-00-00' format are allowed.
- When NO_ZERO_DATE mode is not enabled, dates in the '0000-00-00' format are allowed.
- When NO_ZERO_DATE mode is enabled but strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES) is not enabled, dates in the '0000-00-00' format are allowed.
- When both strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES) and NO_ZERO_DATE mode are enabled, dates in the '0000-00-00' format are not allowed and generate an error.
- When both strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES) and NO_ZERO_DATE mode are enabled and ignore is specified, dates in the '0000-00-00' format are allowed.
- NO_ZERO_IN_DATE: Allows log formats where the year is non-zero and the month or day is 0 (e.g., '2010-00-01' or '2010-01-00').
- When NO_ZERO_IN_DATE mode is not enabled, dates where the year is non-zero and the month or day is 0 are allowed.
- When NO_ZERO_IN_DATE mode is enabled but strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES) is not enabled, dates where the year is non-zero and the month or day is 0 are converted to the '0000-00-00' format.
- When both strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES) and NO_ZERO_IN_DATE mode are enabled, dates where the year is non-zero and the month or day is 0 are not allowed and generate an error.
- When both strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES) and NO_ZERO_IN_DATE mode are enabled and ignore is specified, dates where the year is non-zero and the month or day is 0 are converted to the '0000-00-00' format.
- ONLY_FULL_GROUP_BY: Requires that the SELECT list, HAVING conditions, or ORDER BY columns contain only columns uniquely determined by the GROUP BY columns.
- PIPES_AS_CONCAT: Treats (\
|
\ |
) is treated as a string concatenation operator (the same as CONCAT()) rather than a synonym for OR. PAD_CHAR_TO_FULL_LENGTH: Preserves trailing spaces in a column during a CHAR search. The retrieved CHAR values are also padded to their full length.REAL_AS_FLOAT: By default, REAL is considered a synonym for DOUBLE. After this option is set, REAL is considered a synonym for FLOAT. STRICT_ALL_TABLES: Enables strict SQL mode for all storage engines, rejecting invalid data values.STRICT_TRANS_TABLES: Enables strict SQL mode for transactional storage engines and, where possible, for non-transactional storage engines.TIME_TRUNCATE_FRACTIONAL: Controls whether rounding occurs when inserting TIME, DATE, or TIMESTAMP values with fractional seconds into columns of the same type but with fewer decimal places. By default, rounding occurs; if this mode is enabled, truncation occurs instead. ANSI: Equivalent to the combination of REAL_AS_FLOAT, PIPES_AS_CONCAT, ANSI_QUOTES, IGNORE_SPACE, and ONLY_FULL_GROUP_BY. DB2: Equivalent to the combination of PIPES_AS_CONCAT, ANSI_QUOTES, IGNORE_SPACE, NO_KEY_OPTIONS, NO_TABLE_OPTIONS, and NO_FIELD_OPTIONS.MAXDB: Equivalent to the combination of PIPES_AS_CONCAT, ANSI_QUOTES, IGNORE_SPACE, NO_KEY_OPTIONS, NO_TABLE_OPTIONS, NO_FIELD_OPTIONS, and NO_AUTO_CREATE_USER. MSSQL: Equivalent to the combination of PIPES_AS_CONCAT, ANSI_QUOTES, IGNORE_SPACE, NO_KEY_OPTIONS, NO_TABLE_OPTIONS, and NO_FIELD_OPTIONS.MYSQL323: Equivalent to HIGH_NOT_PRECEDENCE with additional MYSQL323 features.MYSQL40: Equivalent to HIGH_NOT_PRECEDENCE with additional MYSQL40 features.POSTGRESQL: Equivalent to the combination of PIPES_AS_CONCAT, ANSI_QUOTES, IGNORE_SPACE, NO_KEY_OPTIONS, NO_TABLE_OPTIONS, and NO_FIELD_OPTIONS. |