ClustrixDB uses MySQL syntax but was built from the ground up to be a distributed, shared-nothing database. Any application that uses a MySQL client or JDBC/ODBC drivers, like Ruby on Rails or Hibernate, can connect to ClustrixDB without issue and use standard MySQL constructs to interact with ClustrixDB. The following sections describe ClustrixDB-specific syntax and caveats for MySQL compatibility.

MySQL Compatibility

ClustrixDB aims to provide support for most standard MySQL functionality. While we do not synchronize our feature development with MySQL releases, we strive to provide the features and functions required by our customers to successfully run production environments. We monitor both our customers' requirements and new MySQL functionality to determine our feature roadmap and use recent shipping releases of MySQL as part of an automated QA process for compatibility. 

ClustrixDB supports:

• SQL 
• Partitioned Tables (range only) 
• Stored Routines
• Triggers

See also:

• Unsupported Features
• General Differences from MySQL
• Data Types

About ClustrixDB Internals:

ClustrixDB is a clustered, distributed database built from the ground up for scale, concurrency, and performance as well as ease of use. While ClustrixDB seeks to be MySQL compatible, it contains no actual MySQL source code.

Here is more on ClustrixDB internals:

• Written primarily in C
• Distributed, shared-nothing architecture with:
  • Automatic distribution across nodes
  • Distributed evaluation model
• Implements a transactional storage engine that most closely matches the specifications for InnoDB, including providing support for referential integrity and foreign key constraints
• Automatically retains multiple copies of all data to provide redundancy and fault tolerance

ENGINE TYPE

ClustrixDB most closely emulates the interface of the InnoDB storage engine. All tables in ClustrixDB are fully transactional and ACID-compliant and use the MVCC model for concurrency control. Engine types supported include memory, clustrix, ndb, and ndbcluster. If another Engine Type is specified, ClustrixDB will accept the syntax but continue to use the Clustrix engine. 

Additional Information

For additional information on ClustrixDB and MySQL Compatibility, please see one of the following pages:

• General Differences from MySQL
  • ClustrixDB versus MySQL Privileges
  • Unsupported Features
• ClustrixDB SQL and DDL
  • ALTER CLUSTER Syntax
  • Consistent Order
  • Data Types
  • Fractional Seconds
  • Generated Columns
  • In-Memory Tables
  • Invisible Indexes
  • JSON
  • Partitioned Tables
  • Stored Routines
  • Triggers
• Evaluating ClustrixDB Compatibility and Performance
• ClustrixDB Version and MySQL Version Compatibility