SELECT query statements are supported. A small number of keywords and syntax within SELECT statements are not supported. For details, see SELECT Statement Description.SET [ SESSION | GLOBAL ] sql_mode='modes' statement. It also supports querying the current SQL Mode using SELECT @@sql_mode.NO_AUTO_CREATE_USER and NO_ENGINE_SUBSTITUTION.Term | Description |
PIPES_AS_CONCAT | Treats || as the string concatenation operator (+) (same as CONCAT()), not as OR. |
ANSI_QUOTES | Treats " as an identifier. After ANSI_QUOTES is enabled, only the content within single quotes is treated as a string literal, and double quotes are interpreted as identifiers. Therefore, you cannot use double quotes to quote strings. |
IGNORE_SPACE | When this mode is enabled, the system ignores spaces. For example, user and user are treated as the same. |
ONLY_FULL_GROUP_BY | If a column that is not processed by an aggregate function or not included in GROUP BY appears in SELECT, HAVING, or ORDER BY, the SQL statement is invalid. |
NO_UNSIGNED_SUBTRACTION | In subtraction, if an operand has no sign, the result is not marked as UNSIGNED. |
NO_BACKSLASH_ESCAPES | When this mode is enabled, the backslash symbol \\ represents only itself. |
STRICT_TRANS_TABLES | Enables strict mode for transactional storage engines and rolls back the entire statement after an invalid value is inserted. |
STRICT_ALL_TABLES | For transactional tables, rolls back the entire transaction statement after an invalid value is written. |
NO_ZERO_IN_DATE | In strict mode, dates with a month or day part of 0 are not accepted. If the IGNORE option is used, such dates are inserted as 0000-00-00. In non-strict mode, the date is accepted, but a warning is generated. |
NO_ZERO_DATE | In strict mode, 0000-00-00 is not treated as a valid date. You can still use the IGNORE option to insert a zero date. In non-strict mode, the date is accepted, but a warning is generated. |
ALLOW_INVALID_DATES | Does not check the validity of the entire date, but only checks whether the month value is between 1 and 12 and whether the day value is between 1 and 31. Applies only to DATE and DATETIME columns. TIMESTAMP columns require a full validity check. |
ERROR_FOR_DIVISION_BY_ZERO | When this mode is enabled, the system generates an error if the divisor is 0 during an INSERT or UPDATE operation. When this mode is not enabled, the system generates a warning and replaces the result with NULL if the divisor is 0. |
REAL_AS_FLOAT | Treats REAL as a synonym for FLOAT, not for DOUBLE. |
NO_DIR_IN_CREATE | Ignores all INDEX DIRECTORY and DATA DIRECTORY directives when a table is created. This option is useful only for replication servers. |
NO_AUTO_CREATE_USER | Prevents GRANT from automatically creating new users (except when a password is specified). Has no practical effect in a read-only analysis instance. |
NO_ENGINE_SUBSTITUTION | Prevents the storage engine from being automatically substituted when the required storage engine is disabled or not compiled. Has no practical effect in a read-only analysis instance. |
Character Set | Description | Supported Collation | Maximum Bytes |
utf8 | UTF-8 Unicode | utf8_bin,utf8_general_ci,utf8_unicode_ci | 3 |
utf8mb4 | UTF-8 Unicode | utf8mb4_bin,utf8mb4_general_ci,utf8mb4_unicode_ci,utf8mb4_0900_ai_ci,utf8mb4_0900_bin | 4 |
SELECT ... GROUP BY expr queries, and the returned results are consistent with those in MySQL 8.0. By default, the results are not sorted.Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback