Limitations

MatrixOne is compatible with a commonly used subset of MySQL, not all of MySQL 8.0. The following boundaries are important to understand before copying syntax from the upstream MySQL manual into production.

Limitations may be relaxed in later versions. Use error messages from the current instance and the release notes as the final authority.

LOAD DATA

The following parts of the complete MySQL LOAD DATA syntax are commonly unsupported or only partially supported in MatrixOne:

Item

Description

LOCAL

Uploading a client-local file to the server through a LOCAL path is not supported.

REPLACE

REPLACE semantics during loading are generally unavailable.

PARTITION

Loading into a specified partition is generally unsupported.

CHARACTER SET

Data is effectively handled as UTF-8.

Arbitrary field or line delimiters

Delimiters are supported, but some escapes, variable ENCLOSED BY, LINES STARTING BY, and similar options are constrained by the CSV implementation.

SET col = expr

Column-expression transformations during loading are generally unsupported.

User-variable columns

Behaviors such as filtering through @user_var placeholders are limited.

Recommended usage pattern:

LOAD DATA INFILE 'path/to/file'
[IGNORE]
INTO TABLE tbl
FIELDS TERMINATED BY ','
[IGNORE n LINES]
[(col_list)];

Summary of CSV conventions:

  • Field delimiter: Usually ,, though other non-special delimiters such as | can be used.

  • Field quote: ".

  • Line ending: \n or \r\n.

  • \N represents NULL.

  • Lines beginning with # are commonly skipped as comments.

  • IGNORE: When conversion fails, continue where possible and accumulate warnings instead of failing the entire batch. Exact behavior depends on the engine.

For large files, prefer loading from a Stage and server-side path instead of relying on client-side LOCAL.

Partitioning

Instances with partitioning enabled support creating partitioned tables with KEY, HASH, RANGE, RANGE COLUMNS, LIST, and LIST COLUMNS. RANGE and LIST partitions check incoming data. An insert fails if no partition matches a value.

  • RANGE: Use VALUES LESS THAN to define an exclusive upper bound for each partition. To accept values greater than or equal to the final finite upper bound, define the last partition with VALUES LESS THAN (MAXVALUE).

  • LIST: Use VALUES IN to specify the values accepted by each partition. Values that match no partition cannot be inserted.

  • Subpartitioning and foreign keys on partitioned tables are not supported.

Partitioning capabilities may vary by instance version and configuration. Before using partitioning, verify table creation, valid inserts, and out-of-range inserts on the target instance. See System Tables for how to view partition definitions.

See Partition support and limitations for detailed rules and examples.

JDBC and driver capabilities

Official JDBC and other drivers use a supported-feature list for MatrixOne. Common CRUD, prepared-statement, and batch operations are supported, while some proprietary or uncommon MySQL Connector APIs may not be implemented. During integration, refer to Developer and the driver release notes. Do not assume behavior is 100% identical to MySQL Connector/J.

Other common differences

Area

Description

Reserved keywords

They differ slightly from MySQL. Reserved words in qualified names should still be enclosed in backticks. See Structure and Syntax.

System tables

information_schema / mysql are subsets.

Vector columns

They cannot be primary or unique keys, and dimensions and element types are constrained. See Data Types.

Stored procedures / triggers / event scheduler

Do not assume they are available. Refer to the syntax actually supported by the instance.

Character sets

Product workflows primarily use utf8mb4.

Detailed reference

Last updated on