メタデータの末尾にスキップ
メタデータの先頭に移動

Clustrix is highly compatible with MySQL, but because the architectures are fundamentally different, certain behaviors differ. This topic lists MySQL functionality that Clustrix does not support. For a description of features that are supported but differ from the MySQL implementation, see Feature Differences.

Unsupported Data Types

  • Spatial Extensions

サポートされない機能

  • Triggers (coming soon!)
  • Full-Text Search
  • XML Functions
  • MySQL Performance Schema
  • The SET NAMES ASCII option. Use SET NAMES LATIN1 instead
  • MySQL's implementation-specific global variables, such as "innodb" variables
  • SELECT INTO ... OUTFILE option. Clustrix does support the LOAD DATA INFILE command.

Unsupported Functions

  • ANALYSE()
  • BENCHMARK()
  • CHARSET()
  • COERCIBILITY()
  • COLLATION()
  • CURRENT_USER()
  • EXTRACT()
  • GET_FORMAT()
  • GET_LOCK()
  • IS_FREE_LOCK()
  • LOAD_FILE()
  • MAKEDATE()
  • RELEASE_LOCK()
  • ROW_COUNT()
  • SESSION_USER()
  • SLEEP()

サポートされない権限

The following MySQL privileges are not supported, and generate a syntax error if used in a GRANT statement:

  • EVENT
  • TRIGGER (coming soon!)

以下の権限は無視されます:

  • FILE
  • LOCK TABLES
  • PROCESS
  • REFERENCES
  • RELOAD
  • SHOW DATABASES
  • SHOW VIEW
  • SHUTDOWN

Unsupported Statements

  • CHECKSUM TABLE

Miscellaneous

  • The _ and % wild cards are not supported in database names.
  • GRANT ステートメントは REQUIRE が含まれていても無視します。
  • viewのためのDEFINER および SQL SECURITY 引数は無視されます。

The variables are not supported and generate a syntax error:

  • MAX_QUERIES_PER_HOUR
  • MAX_UPDATES_PER_HOUR
  • MAX_CONNECTIONS_PER_HOUR
  • MAX_USER_CONNECTIONS
  • RENAME USER, CURRENT_USER, CURRENT_USER() および SESSION_USER() はサポートされていません。
  • UNSOFTFAIL option is not available
  • RENAME DATABASE

SQL_MODE

Clustrix emulates the default SQL mode behavior and supports  NO_AUTO_VALUE_ON_ZERO. Other values for SQL_MODE are not supported

TOP
inserted by FC2 system