This topic lists MySQL functionality that ClustrixDB does not support. For a description of features that are supported but differ from the MySQL implementation, see the section on MySQL Compatibility.
Please see Unsupported SQL (in the ClustrixDB SQL and DDL section)
Unsupported Data Types
- Spatial Extensions
- Full Text Search
- XML Functions (limited support only)
- MySQL Performance Schema
- The SET NAMES ASCII option. Use SET NAMES LATIN1 instead
- SELECT INTO ... OUTFILE option. ClustrixDB does support the LOAD DATA INFILE command
Instead, if there is a MySQL client installed on remote machine, run the following to generate the file on the client host:
shell> mysql -e "SELECT ..." > file_name
The following MySQL privileges are not supported, and generate a syntax error if used in a GRANT statement:
The following privileges are ignored:
- LOCK TABLES
- SHOW DATABASES
- SHOW VIEW
- CHECKSUM TABLE
- RENAME USER
- SHOW WARNINGS
- ClustrixDB accepts this syntax but will not show any warnings.
- The _ and % wild cards are not supported in database names.
- The GRANT statement ignores REQUIRE, if included.
- The DEFINER and SQL SECURITY arguments for views are ignored.
The following variables are not supported and generate a syntax error:
ClustrixDB emulates the default SQL mode behavior and supports NO_AUTO_VALUE_ON_ZERO. Other values for SQL_MODE are not supported.
ClustrixDB does not support MySQL 5.7 GTIDs for replication. To replicate to or from MySQL 5.7, disable the GTID functionality as described in Using ClustrixDB as a Replication Master or Using ClustrixDB as a Replication Slave.