From 45a5cd8881519e564e9778495d9d7395e2a3ce47 Mon Sep 17 00:00:00 2001 From: qiancai Date: Fri, 24 Oct 2025 09:27:11 +0800 Subject: [PATCH 1/4] Update mysql-compatibility.md --- mysql-compatibility.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/mysql-compatibility.md b/mysql-compatibility.md index 6dfdef055255d..f182c701be856 100644 --- a/mysql-compatibility.md +++ b/mysql-compatibility.md @@ -46,6 +46,11 @@ You can try out TiDB features on [TiDB Playground](https://play.tidbcloud.com/?u + Events + User-defined functions + `FULLTEXT` syntax and indexes [#1793](https://github.com/pingcap/tidb/issues/1793) + + >**Note:** + > + > Currently, only {{{ .starter }} and {{{ .essential }}} clusters in certain AWS regions support [`FULLTEXT` syntax and indexes](/tidb-cloud/vector-search-full-text-search-sql.md). TiDB Self-Managed and TiDB Cloud Dedicated do not support `FULLTEXT` syntax and indexes. + + `SPATIAL` (also known as `GIS`/`GEOMETRY`) functions, data types and indexes [#6347](https://github.com/pingcap/tidb/issues/6347) + Character sets other than `ascii`, `latin1`, `binary`, `utf8`, `utf8mb4`, and `gbk`. + Optimizer trace From a333b99a6e5fb0168abafb224b2070c4b502fe6d Mon Sep 17 00:00:00 2001 From: qiancai Date: Fri, 24 Oct 2025 09:42:00 +0800 Subject: [PATCH 2/4] modified the note --- mysql-compatibility.md | 2 +- sql-statements/sql-statement-add-index.md | 7 ++++++- sql-statements/sql-statement-create-index.md | 7 ++++++- sql-statements/sql-statement-create-table.md | 7 ++++++- 4 files changed, 19 insertions(+), 4 deletions(-) diff --git a/mysql-compatibility.md b/mysql-compatibility.md index f182c701be856..58f338ed29399 100644 --- a/mysql-compatibility.md +++ b/mysql-compatibility.md @@ -49,7 +49,7 @@ You can try out TiDB features on [TiDB Playground](https://play.tidbcloud.com/?u >**Note:** > - > Currently, only {{{ .starter }} and {{{ .essential }}} clusters in certain AWS regions support [`FULLTEXT` syntax and indexes](/tidb-cloud/vector-search-full-text-search-sql.md). TiDB Self-Managed and TiDB Cloud Dedicated do not support `FULLTEXT` syntax and indexes. + > Currently, only {{{ .starter }} and {{{ .essential }}} clusters in certain AWS regions support [`FULLTEXT` syntax and indexes](/tidb-cloud/vector-search-full-text-search-sql.md). TiDB Self-Managed and TiDB Cloud Dedicated support parsing the `FULLTEXT` syntax but do not support using the `FULLTEXT` indexes. + `SPATIAL` (also known as `GIS`/`GEOMETRY`) functions, data types and indexes [#6347](https://github.com/pingcap/tidb/issues/6347) + Character sets other than `ascii`, `latin1`, `binary`, `utf8`, `utf8mb4`, and `gbk`. diff --git a/sql-statements/sql-statement-add-index.md b/sql-statements/sql-statement-add-index.md index d071027fb4e44..dd2355fd03984 100644 --- a/sql-statements/sql-statement-add-index.md +++ b/sql-statements/sql-statement-add-index.md @@ -97,7 +97,12 @@ mysql> EXPLAIN SELECT * FROM t1 WHERE c1 = 3; * TiDB accepts index types such as `HASH`, `BTREE` and `RTREE` in syntax for compatibility with MySQL, but ignores them. * `SPATIAL` indexes are not supported. -* TiDB supports parsing the `FULLTEXT` syntax but does not support using the `FULLTEXT` indexes. +* TiDB Self-Managed and TiDB Cloud Dedicated supports parsing the `FULLTEXT` syntax but does not support using the `FULLTEXT` indexes. + + >**Note:** + > + > Currently, only {{{ .starter }} and {{{ .essential }}} clusters in certain AWS regions support [`FULLTEXT` syntax and indexes](/tidb-cloud/vector-search-full-text-search-sql.md). + * Descending indexes are not supported (similar to MySQL 5.7). * Adding the primary key of the `CLUSTERED` type to a table is not supported. For more details about the primary key of the `CLUSTERED` type, refer to [clustered index](/clustered-indexes.md). * Setting a `PRIMARY KEY` or `UNIQUE INDEX` as a [global index](/partitioned-table.md#global-indexes) with the `GLOBAL` index option is a TiDB extension for [partitioned tables](/partitioned-table.md) and is not compatible with MySQL. diff --git a/sql-statements/sql-statement-create-index.md b/sql-statements/sql-statement-create-index.md index 507660813f1bc..fc49b15d31b31 100644 --- a/sql-statements/sql-statement-create-index.md +++ b/sql-statements/sql-statement-create-index.md @@ -385,7 +385,12 @@ The system variables associated with the `CREATE INDEX` statement are `tidb_ddl_ ## MySQL compatibility -* TiDB supports parsing the `FULLTEXT` syntax but does not support using the `FULLTEXT`, `HASH`, and `SPATIAL` indexes. +* TiDB Self-Managed and TiDB Cloud Dedicated support parsing the `FULLTEXT` syntax but do not support using the `FULLTEXT`, `HASH`, and `SPATIAL` indexes. + + >**Note:** + > + > Currently, only {{{ .starter }} and {{{ .essential }}} clusters in certain AWS regions support [`FULLTEXT` syntax and indexes](/tidb-cloud/vector-search-full-text-search-sql.md). + * TiDB accepts index types such as `HASH`, `BTREE` and `RTREE` in syntax for compatibility with MySQL, but ignores them. * Descending indexes are not supported (similar to MySQL 5.7). * Adding the primary key of the `CLUSTERED` type to a table is not supported. For more details about the primary key of the `CLUSTERED` type, refer to [clustered index](/clustered-indexes.md). diff --git a/sql-statements/sql-statement-create-table.md b/sql-statements/sql-statement-create-table.md index 35b506ecb57d0..99e9b66fa901f 100644 --- a/sql-statements/sql-statement-create-table.md +++ b/sql-statements/sql-statement-create-table.md @@ -273,7 +273,12 @@ mysql> DESC t1; * All of the data types except spatial types are supported. * TiDB accepts index types such as `HASH`, `BTREE` and `RTREE` in syntax for compatibility with MySQL, but ignores them. -* TiDB supports parsing the `FULLTEXT` syntax but does not support using the `FULLTEXT` indexes. +* TiDB Self-Managed and TiDB Cloud Dedicated support parsing the `FULLTEXT` syntax but do not support using the `FULLTEXT` indexes. + + >**Note:** + > + > Currently, only {{{ .starter }} and {{{ .essential }}} clusters in certain AWS regions support [`FULLTEXT` syntax and indexes](/tidb-cloud/vector-search-full-text-search-sql.md). + * Setting a `PRIMARY KEY` or `UNIQUE INDEX` as a [global index](/partitioned-table.md#global-indexes) with the `GLOBAL` index option is a TiDB extension for [partitioned tables](/partitioned-table.md) and is not compatible with MySQL. From 8736a3ffbcb5a045956a9a8e6a4d4c7d83160b23 Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Tue, 28 Oct 2025 08:39:46 +0800 Subject: [PATCH 3/4] Apply suggestions from code review Co-authored-by: xixirangrang --- mysql-compatibility.md | 2 +- sql-statements/sql-statement-add-index.md | 2 +- sql-statements/sql-statement-create-index.md | 2 +- sql-statements/sql-statement-create-table.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/mysql-compatibility.md b/mysql-compatibility.md index 58f338ed29399..c3a4ca27ee554 100644 --- a/mysql-compatibility.md +++ b/mysql-compatibility.md @@ -49,7 +49,7 @@ You can try out TiDB features on [TiDB Playground](https://play.tidbcloud.com/?u >**Note:** > - > Currently, only {{{ .starter }} and {{{ .essential }}} clusters in certain AWS regions support [`FULLTEXT` syntax and indexes](/tidb-cloud/vector-search-full-text-search-sql.md). TiDB Self-Managed and TiDB Cloud Dedicated support parsing the `FULLTEXT` syntax but do not support using the `FULLTEXT` indexes. + > Currently, only {{{ .starter }} and {{{ .essential }}} clusters in certain AWS regions support [`FULLTEXT` syntax and indexes](https://docs.pingcap.com/tidbcloud/vector-search-full-text-search-sql). TiDB Self-Managed and TiDB Cloud Dedicated support parsing the `FULLTEXT` syntax but do not support using the `FULLTEXT` indexes. + `SPATIAL` (also known as `GIS`/`GEOMETRY`) functions, data types and indexes [#6347](https://github.com/pingcap/tidb/issues/6347) + Character sets other than `ascii`, `latin1`, `binary`, `utf8`, `utf8mb4`, and `gbk`. diff --git a/sql-statements/sql-statement-add-index.md b/sql-statements/sql-statement-add-index.md index dd2355fd03984..9a7039ffe3812 100644 --- a/sql-statements/sql-statement-add-index.md +++ b/sql-statements/sql-statement-add-index.md @@ -101,7 +101,7 @@ mysql> EXPLAIN SELECT * FROM t1 WHERE c1 = 3; >**Note:** > - > Currently, only {{{ .starter }} and {{{ .essential }}} clusters in certain AWS regions support [`FULLTEXT` syntax and indexes](/tidb-cloud/vector-search-full-text-search-sql.md). + > Currently, only {{{ .starter }} and {{{ .essential }}} clusters in certain AWS regions support [`FULLTEXT` syntax and indexes](https://docs.pingcap.com/tidbcloud/vector-search-full-text-search-sql). * Descending indexes are not supported (similar to MySQL 5.7). * Adding the primary key of the `CLUSTERED` type to a table is not supported. For more details about the primary key of the `CLUSTERED` type, refer to [clustered index](/clustered-indexes.md). diff --git a/sql-statements/sql-statement-create-index.md b/sql-statements/sql-statement-create-index.md index fc49b15d31b31..4bb62620f16d2 100644 --- a/sql-statements/sql-statement-create-index.md +++ b/sql-statements/sql-statement-create-index.md @@ -389,7 +389,7 @@ The system variables associated with the `CREATE INDEX` statement are `tidb_ddl_ >**Note:** > - > Currently, only {{{ .starter }} and {{{ .essential }}} clusters in certain AWS regions support [`FULLTEXT` syntax and indexes](/tidb-cloud/vector-search-full-text-search-sql.md). + > Currently, only {{{ .starter }} and {{{ .essential }}} clusters in certain AWS regions support [`FULLTEXT` syntax and indexes](https://docs.pingcap.com/tidbcloud/vector-search-full-text-search-sql). * TiDB accepts index types such as `HASH`, `BTREE` and `RTREE` in syntax for compatibility with MySQL, but ignores them. * Descending indexes are not supported (similar to MySQL 5.7). diff --git a/sql-statements/sql-statement-create-table.md b/sql-statements/sql-statement-create-table.md index 99e9b66fa901f..a166fd021df44 100644 --- a/sql-statements/sql-statement-create-table.md +++ b/sql-statements/sql-statement-create-table.md @@ -277,7 +277,7 @@ mysql> DESC t1; >**Note:** > - > Currently, only {{{ .starter }} and {{{ .essential }}} clusters in certain AWS regions support [`FULLTEXT` syntax and indexes](/tidb-cloud/vector-search-full-text-search-sql.md). + > Currently, only {{{ .starter }} and {{{ .essential }}} clusters in certain AWS regions support [`FULLTEXT` syntax and indexes](https://docs.pingcap.com/tidbcloud/vector-search-full-text-search-sql). * Setting a `PRIMARY KEY` or `UNIQUE INDEX` as a [global index](/partitioned-table.md#global-indexes) with the `GLOBAL` index option is a TiDB extension for [partitioned tables](/partitioned-table.md) and is not compatible with MySQL. From 8f4f7cb6079926bceaac1bfd0baef61548d2cceb Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Tue, 28 Oct 2025 09:37:52 +0800 Subject: [PATCH 4/4] Apply suggestions from code review Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> --- sql-statements/sql-statement-add-index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sql-statements/sql-statement-add-index.md b/sql-statements/sql-statement-add-index.md index 9a7039ffe3812..b09c0d0a93d42 100644 --- a/sql-statements/sql-statement-add-index.md +++ b/sql-statements/sql-statement-add-index.md @@ -97,7 +97,7 @@ mysql> EXPLAIN SELECT * FROM t1 WHERE c1 = 3; * TiDB accepts index types such as `HASH`, `BTREE` and `RTREE` in syntax for compatibility with MySQL, but ignores them. * `SPATIAL` indexes are not supported. -* TiDB Self-Managed and TiDB Cloud Dedicated supports parsing the `FULLTEXT` syntax but does not support using the `FULLTEXT` indexes. +* TiDB Self-Managed and TiDB Cloud Dedicated support parsing the `FULLTEXT` syntax but do not support using the `FULLTEXT` indexes. >**Note:** >