TiDB Features
This document lists the features supported in different TiDB versions, including Long-Term Support (LTS) versions and Development Milestone Release (DMR) versions after the latest LTS version.
You can try out TiDB features on TiDB Playground.
Data types, functions, and operators
Indexing and constraints
SQL statements
Advanced SQL features
Data definition language (DDL)
Transactions
Partitioning
Statistics
Security
Data import and export
Management, observability, and tools
- TiDB incorrectly treats latin1 as a subset of utf8. See TiDB #18955 for more details.↩
- Starting from v6.5.0, the expression indexes created on the functions listed by the
tidb_allow_function_for_expression_indexsystem variable have been tested and can be used in production environments, and more functions will be supported in the future releases. For functions not listed by this variable, the corresponding expression indexes are not recommended for use in production environments. See expression indexes for details.↩ - See Statement Reference for a full list of SQL statements supported.↩
- Starting from v6.4.0, TiDB supports high-performance and globally monotonic
AUTO_INCREMENTcolumns↩ - Starting from TiDB v7.5.0, technical support for the data replication feature of TiDB Binlog is no longer provided. It is strongly recommended to use TiCDC as an alternative solution for data replication. Although TiDB Binlog v7.5.0 still supports the Point-in-Time Recovery (PITR) scenario, this component will be completely deprecated in future versions. It is recommended to use PITR as an alternative solution for data recovery.↩
- Starting from TiDB v7.0.0, the new parameter
FIELDS DEFINED NULL BYand support for importing data from S3 and GCS are experimental features. Starting from v7.6.0, TiDB processesLOAD DATAin transactions in the same way as MySQL. TheLOAD DATAstatement in a transaction no longer automatically commits the current transaction or starts a new transaction. Moreover, you can explicitly commit or roll back theLOAD DATAstatement in a transaction. Additionally, theLOAD DATAstatement is affected by the TiDB transaction mode setting (optimistic or pessimistic transaction).↩