From f167a2e217b30e66acce5139b1b657de5736c721 Mon Sep 17 00:00:00 2001 From: Yasuo Honda Date: Tue, 6 Oct 2026 15:30:57 +0900 Subject: [PATCH] releases: fix an issue link text in the v2.1.16 release notes Co-Authored-By: Claude Opus 5.5 --- releases/release-2.1.16.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/releases/release-2.1.16.md b/releases/release-2.1.16.md index 6cc61b5ce64ef..50f13d5cbf797 100644 --- a/releases/release-2.1.16.md +++ b/releases/release-2.1.16.md @@ -28,7 +28,7 @@ TiDB Ansible version: 2.1.16 - Support `SPLIT TABLE` statements that return the number of Regions that are successfully split and a finished percentage rather than an error when the scheduling is not finished for Region scatter before the timeout [#11487](https://github.com/pingcap/tidb/pull/11487) - Make `REGEXP BINARY` function case sensitive to be compatible with MySQL [#11505](https://github.com/pingcap/tidb/pull/11505) - Fix the issue that `NULL` is not returned correctly because the value of `YEAR` in the `DATE_ADD`/`DATE_SUB` result overflows when it is smaller than 0 or larger than 65535 [#11477](https://github.com/pingcap/tidb/pull/11477) - - Add in the slow query table a `Succ` field that indicates whether the execution succeeds [#11412](https://github.com/pingcap/tidb/pull/11421) + - Add in the slow query table a `Succ` field that indicates whether the execution succeeds [#11421](https://github.com/pingcap/tidb/pull/11421) - Fix the MySQL incompatibility issue caused by fetching the current timestamp multiple times when a SQL statement involves calculations of the current time (such as `CURRENT_TIMESTAMP` or `NOW`) [#11392](https://github.com/pingcap/tidb/pull/11392) - Fix the issue that the AUTO_INCREMENT columns do not handle the FLOAT or DOUBLE type [#11389](https://github.com/pingcap/tidb/pull/11389) - Fix the issue that `NULL` is not returned correctly when the `CONVERT_TZ` function accepts an invalid argument [#11357](https://github.com/pingcap/tidb/pull/11357)