From 5f16e7f0d821fa36642a20417378ec4f66dbc6fb Mon Sep 17 00:00:00 2001 From: Ryosei Sato <132046562+sary8@users.noreply.github.com> Date: Wed, 16 Sep 2026 21:37:51 +0900 Subject: [PATCH 1/5] develop: fix 404 links to the mysql2 documentation The mysql2 documentation is no longer kept in the documentation/en directory of the sidorares/node-mysql2 repository, so the linked URL returns 404. Point it to the current documentation site instead. Ref: https://github.com/pingcap/docs/issues/17075 --- develop/dev-guide-sample-application-aws-lambda.md | 2 +- develop/dev-guide-sample-application-nextjs.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/develop/dev-guide-sample-application-aws-lambda.md b/develop/dev-guide-sample-application-aws-lambda.md index b582a41d77408..5b81833b1f061 100644 --- a/develop/dev-guide-sample-application-aws-lambda.md +++ b/develop/dev-guide-sample-application-aws-lambda.md @@ -360,7 +360,7 @@ For more information, refer to [Delete data](/develop/dev-guide-delete-data.md). ## Next steps - For more details on how to use TiDB in AWS Lambda Function, see our [TiDB-Lambda-integration/aws-lambda-bookstore Demo](https://github.com/pingcap/TiDB-Lambda-integration/blob/main/aws-lambda-bookstore/README.md). You can also use AWS API Gateway to build a RESTful API for your application. -- Learn more usage of `mysql2` from [the documentation of `mysql2`](https://github.com/sidorares/node-mysql2/tree/master/documentation/en). +- Learn more usage of `mysql2` from [the documentation of `mysql2`](https://sidorares.github.io/node-mysql2/docs/documentation). - Learn more usage of AWS Lambda from [the AWS developer guide of `Lambda`](https://docs.aws.amazon.com/lambda/latest/dg/welcome.html). - Learn the best practices for TiDB application development with the chapters in the [Developer guide](/develop/dev-guide-overview.md), such as [Insert data](/develop/dev-guide-insert-data.md), [Update data](/develop/dev-guide-update-data.md), [Delete data](/develop/dev-guide-delete-data.md), [Single table reading](/develop/dev-guide-get-data-from-single-table.md), [Transactions](/develop/dev-guide-transaction-overview.md), and [SQL performance optimization](/develop/dev-guide-optimize-sql-overview.md). - Learn through the professional [TiDB developer courses](https://www.pingcap.com/education/) and earn [TiDB certifications](https://www.pingcap.com/education/certification/) after passing the exam. diff --git a/develop/dev-guide-sample-application-nextjs.md b/develop/dev-guide-sample-application-nextjs.md index 43c63bcf08831..a5b46a4d76aec 100644 --- a/develop/dev-guide-sample-application-nextjs.md +++ b/develop/dev-guide-sample-application-nextjs.md @@ -277,7 +277,7 @@ For more information, refer to [Delete data](/develop/dev-guide-delete-data.md). ## Next steps - For more details on how to build a complex application with ORM and Next.js, see [our Bookshop Demo](https://github.com/pingcap/tidb-prisma-vercel-demo). -- Learn more usage of node-mysql2 driver from [the documentation of node-mysql2](https://github.com/sidorares/node-mysql2/tree/master/documentation/en). +- Learn more usage of node-mysql2 driver from [the documentation of node-mysql2](https://sidorares.github.io/node-mysql2/docs/documentation). - Learn the best practices for TiDB application development with the chapters in the [Developer guide](/develop/dev-guide-overview.md), such as [Insert data](/develop/dev-guide-insert-data.md), [Update data](/develop/dev-guide-update-data.md), [Delete data](/develop/dev-guide-delete-data.md), [Single table reading](/develop/dev-guide-get-data-from-single-table.md), [Transactions](/develop/dev-guide-transaction-overview.md), and [SQL performance optimization](/develop/dev-guide-optimize-sql-overview.md). - Learn through the professional [TiDB developer courses](https://www.pingcap.com/education/) and earn [TiDB certifications](https://www.pingcap.com/education/certification/) after passing the exam. From a8310183b8bd1b3fb75ecc74c5e1361eccfd9898 Mon Sep 17 00:00:00 2001 From: Ryosei Sato <132046562+sary8@users.noreply.github.com> Date: Wed, 16 Sep 2026 21:38:25 +0900 Subject: [PATCH 2/5] *: pin the pingcap/tidb source links to the release-7.1 branch In the master branch of pingcap/tidb, br/pkg/lightning has been moved to lightning, and br/pkg/restore/systable_restore.go has been moved to br/pkg/restore/snap_client, so the linked URLs return 404. Pin them to the release-7.1 branch, which keeps the original paths and matches the TiDB version that this documentation describes. Ref: https://github.com/pingcap/docs/issues/17075 --- br/br-snapshot-guide.md | 2 +- faq/backup-and-restore-faq.md | 2 +- tidb-lightning/tidb-lightning-overview.md | 2 +- tidb-troubleshooting-map.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/br/br-snapshot-guide.md b/br/br-snapshot-guide.md index 7d9b14df0ce90..2c784216a9010 100644 --- a/br/br-snapshot-guide.md +++ b/br/br-snapshot-guide.md @@ -142,7 +142,7 @@ Starting from BR v5.1.0, when you back up snapshots, BR backs up the **system ta - Statistics tables (`mysql.stat_*`) - System variable tables (`mysql.tidb` and `mysql.global_variables`) -- [Other system tables](https://github.com/pingcap/tidb/blob/master/br/pkg/restore/systable_restore.go#L31) +- [Other system tables](https://github.com/pingcap/tidb/blob/release-7.1/br/pkg/restore/systable_restore.go#L31) ``` +-----------------------------------------------------+ diff --git a/faq/backup-and-restore-faq.md b/faq/backup-and-restore-faq.md index a81bf037db021..2f8e8c0c1ce00 100644 --- a/faq/backup-and-restore-faq.md +++ b/faq/backup-and-restore-faq.md @@ -293,7 +293,7 @@ Note that even if you configures [table filter](/table-filter.md#syntax), **BR d - Statistics tables (`mysql.stat_*`) - System variable tables (`mysql.tidb`, `mysql.global_variables`) -- [Other system tables](https://github.com/pingcap/tidb/blob/master/br/pkg/restore/systable_restore.go#L31) +- [Other system tables](https://github.com/pingcap/tidb/blob/release-7.1/br/pkg/restore/systable_restore.go#L31) ### How to deal with the error of `cannot find rewrite rule` during restoration? diff --git a/tidb-lightning/tidb-lightning-overview.md b/tidb-lightning/tidb-lightning-overview.md index 3bb468287ef08..08e98cd148a61 100644 --- a/tidb-lightning/tidb-lightning-overview.md +++ b/tidb-lightning/tidb-lightning-overview.md @@ -5,7 +5,7 @@ summary: Learn about Lightning and the whole architecture. # TiDB Lightning Overview -[TiDB Lightning](https://github.com/pingcap/tidb/tree/master/br/pkg/lightning) is a tool used for importing data at TB scale to TiDB clusters. It is often used for initial data import to TiDB clusters. +[TiDB Lightning](https://github.com/pingcap/tidb/tree/release-7.1/br/pkg/lightning) is a tool used for importing data at TB scale to TiDB clusters. It is often used for initial data import to TiDB clusters. TiDB Lightning supports the following file formats: diff --git a/tidb-troubleshooting-map.md b/tidb-troubleshooting-map.md index ffccc91beee18..a5a9fa010766b 100644 --- a/tidb-troubleshooting-map.md +++ b/tidb-troubleshooting-map.md @@ -517,7 +517,7 @@ Check the specific cause for busy by viewing the monitor **Grafana** -> **TiKV** ### 6.3 TiDB Lightning -- 6.3.1 TiDB Lightning is a tool for fast full import of large amounts of data into a TiDB cluster. See [TiDB Lightning on GitHub](https://github.com/pingcap/tidb/tree/master/br/pkg/lightning). +- 6.3.1 TiDB Lightning is a tool for fast full import of large amounts of data into a TiDB cluster. See [TiDB Lightning on GitHub](https://github.com/pingcap/tidb/tree/release-7.1/br/pkg/lightning). - 6.3.2 Import speed is too slow. From d2be18d5696a0e7e10ea57ce31142049ca5f6856 Mon Sep 17 00:00:00 2001 From: Ryosei Sato <132046562+sary8@users.noreply.github.com> Date: Wed, 16 Sep 2026 21:39:14 +0900 Subject: [PATCH 3/5] releases: fix 404 links to the contributor GitHub profiles A trailing brace was included in the URL of the AilinKid profile, and the zhangjinpeng1987 account has been renamed to zhangjinpeng87, so both links return 404. These links have already been corrected in the master branch by #17041. Ref: https://github.com/pingcap/docs/issues/17075 --- releases/release-6.5.7.md | 4 ++-- releases/release-7.1.3.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/releases/release-6.5.7.md b/releases/release-6.5.7.md index 515d9d4e4d3d7..2bbb8f59e2bac 100644 --- a/releases/release-6.5.7.md +++ b/releases/release-6.5.7.md @@ -48,7 +48,7 @@ Quick access: [Quick start](https://docs.pingcap.com/tidb/v6.5/quick-start-with- - Fix the issue that TiDB server might consume a significant amount of resources when the enterprise plugin for audit logging is used [#49273](https://github.com/pingcap/tidb/issues/49273) @[lcwangchao](https://github.com/lcwangchao) - Fix the incorrect error message for `ErrLoadDataInvalidURI` (invalid S3 URI error) [#48164](https://github.com/pingcap/tidb/issues/48164) @[lance6716](https://github.com/lance6716) - Fix the issue that high CPU usage of TiDB occurs due to long-term memory pressure caused by `tidb_server_memory_limit` [#48741](https://github.com/pingcap/tidb/issues/48741) @[XuHuaiyu](https://github.com/XuHuaiyu) - - Fix the issue that queries containing common table expressions (CTEs) unexpectedly get stuck when the memory limit is exceeded [#49096](https://github.com/pingcap/tidb/issues/49096) @[AilinKid](https://github.com/AilinKid}) + - Fix the issue that queries containing common table expressions (CTEs) unexpectedly get stuck when the memory limit is exceeded [#49096](https://github.com/pingcap/tidb/issues/49096) @[AilinKid](https://github.com/AilinKid) - Fix the issue that the same query plan has different `PLAN_DIGEST` values in some cases [#47634](https://github.com/pingcap/tidb/issues/47634) @[King-Dylan](https://github.com/King-Dylan) - Fix the issue that queries containing CTEs report `runtime error: index out of range [32] with length 32` when `tidb_max_chunk_size` is set to a small value [#48808](https://github.com/pingcap/tidb/issues/48808) @[guo-shaoge](https://github.com/guo-shaoge) - Fix the issue that TiDB server might panic during graceful shutdown [#36793](https://github.com/pingcap/tidb/issues/36793) @[bb7133](https://github.com/bb7133) @@ -92,5 +92,5 @@ Quick access: [Quick start](https://docs.pingcap.com/tidb/v6.5/quick-start-with- + TiCDC - - Fix the issue that `checkpoint-ts` might get stuck when TiCDC replicates data to downstream MySQL [#10334](https://github.com/pingcap/tiflow/issues/10334) @[zhangjinpeng1987](https://github.com/zhangjinpeng1987) + - Fix the issue that `checkpoint-ts` might get stuck when TiCDC replicates data to downstream MySQL [#10334](https://github.com/pingcap/tiflow/issues/10334) @[zhangjinpeng87](https://github.com/zhangjinpeng87) - Fix the potential data race issue during `kv-client` initialization [#10095](https://github.com/pingcap/tiflow/issues/10095) @[3AceShowHand](https://github.com/3AceShowHand) diff --git a/releases/release-7.1.3.md b/releases/release-7.1.3.md index 7223f04f4fd9e..d9c2146904149 100644 --- a/releases/release-7.1.3.md +++ b/releases/release-7.1.3.md @@ -55,7 +55,7 @@ Quick access: [Quick start](https://docs.pingcap.com/tidb/v7.1/quick-start-with- + TiDB - - Fix the issue that queries containing common table expressions (CTEs) unexpectedly get stuck when the memory limit is exceeded [#49096](https://github.com/pingcap/tidb/issues/49096) @[AilinKid](https://github.com/AilinKid}) + - Fix the issue that queries containing common table expressions (CTEs) unexpectedly get stuck when the memory limit is exceeded [#49096](https://github.com/pingcap/tidb/issues/49096) @[AilinKid](https://github.com/AilinKid) - Fix the issue that high CPU usage of TiDB occurs due to long-term memory pressure caused by `tidb_server_memory_limit` [#48741](https://github.com/pingcap/tidb/issues/48741) @[XuHuaiyu](https://github.com/XuHuaiyu) - Fix the issue that queries containing CTEs report `runtime error: index out of range [32] with length 32` when `tidb_max_chunk_size` is set to a small value [#48808](https://github.com/pingcap/tidb/issues/48808) @[guo-shaoge](https://github.com/guo-shaoge) - Fix the issue that the query result is incorrect when an `ENUM` type column is used as the join key [#48991](https://github.com/pingcap/tidb/issues/48991) @[winoros](https://github.com/winoros) From 6b8693c6d1db8d542026c99f1b6bf1ffd320c14e Mon Sep 17 00:00:00 2001 From: lilin90 Date: Fri, 18 Sep 2026 14:36:54 +0800 Subject: [PATCH 4/5] Update mysql2 docs links Refresh the node-mysql2 documentation links in the sample application guides to point to the current docs site. This keeps the connection pool and prepared statement references consistent across the AWS Lambda, Next.js, and Node.js sample docs. --- develop/dev-guide-sample-application-aws-lambda.md | 6 +++--- develop/dev-guide-sample-application-nextjs.md | 4 ++-- develop/dev-guide-sample-application-nodejs-mysql2.md | 4 ++-- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/develop/dev-guide-sample-application-aws-lambda.md b/develop/dev-guide-sample-application-aws-lambda.md index 5b81833b1f061..817a2821994af 100644 --- a/develop/dev-guide-sample-application-aws-lambda.md +++ b/develop/dev-guide-sample-application-aws-lambda.md @@ -351,9 +351,9 @@ For more information, refer to [Delete data](/develop/dev-guide-delete-data.md). ## Useful notes -- Using [connection pools](https://github.com/sidorares/node-mysql2#using-connection-pools) to manage database connections can reduce the performance overhead caused by frequently establishing and destroying connections. -- To avoid SQL injection, it is recommended to use [prepared statements](https://github.com/sidorares/node-mysql2#using-prepared-statements). -- In scenarios where there are not many complex SQL statements involved, using ORM frameworks like [Sequelize](https://sequelize.org/), [TypeORM](https://typeorm.io/), or [Prisma](https://www.prisma.io/) can greatly improve development efficiency. +- Using [connection pools](https://sidorares.github.io/node-mysql2/docs#using-connection-pools) to manage database connections can reduce the performance overhead caused by frequently establishing and destroying connections. +- To avoid SQL injection, it is recommended to use [prepared statements](https://sidorares.github.io/node-mysql2/docs#using-prepared-statements). +- In scenarios where there are not many complex SQL statements involved, using ORM frameworks like [Sequelize](https://sequelize.org/), [TypeORM](https://typeorm.io/), or [Prisma](https://www.prisma.io/) can greatly improve development efficiency. - For building a RESTful API for your application, it is recommended to [use AWS Lambda with API Gateway](https://docs.aws.amazon.com/lambda/latest/dg/services-apigateway.html). - For designing high-performance applications using TiDB Serverless and AWS Lambda, refer to [this blog](https://aws.amazon.com/blogs/apn/designing-high-performance-applications-using-serverless-tidb-cloud-and-aws-lambda/). diff --git a/develop/dev-guide-sample-application-nextjs.md b/develop/dev-guide-sample-application-nextjs.md index a5b46a4d76aec..144c45e25f968 100644 --- a/develop/dev-guide-sample-application-nextjs.md +++ b/develop/dev-guide-sample-application-nextjs.md @@ -270,8 +270,8 @@ For more information, refer to [Delete data](/develop/dev-guide-delete-data.md). ## Useful notes -- Using [connection pools](https://github.com/sidorares/node-mysql2#using-connection-pools) to manage database connections can reduce the performance overhead caused by frequently establishing and destroying connections. -- To avoid SQL injection, it is recommended to use [prepared statements](https://github.com/sidorares/node-mysql2#using-prepared-statements). +- Using [connection pools](https://sidorares.github.io/node-mysql2/docs#using-connection-pools) to manage database connections can reduce the performance overhead caused by frequently establishing and destroying connections. +- To avoid SQL injection, it is recommended to use [prepared statements](https://sidorares.github.io/node-mysql2/docs#using-prepared-statements). - In scenarios where there are not many complex SQL statements involved, using ORM frameworks like [Sequelize](https://sequelize.org/), [TypeORM](https://typeorm.io/), or [Prisma](https://www.prisma.io/) can greatly improve development efficiency. ## Next steps diff --git a/develop/dev-guide-sample-application-nodejs-mysql2.md b/develop/dev-guide-sample-application-nodejs-mysql2.md index 12dca4fe4d656..e11b05fb2312a 100644 --- a/develop/dev-guide-sample-application-nodejs-mysql2.md +++ b/develop/dev-guide-sample-application-nodejs-mysql2.md @@ -297,8 +297,8 @@ For more information, refer to [Delete data](/develop/dev-guide-delete-data.md). ## Useful notes -- Using [connection pools](https://github.com/sidorares/node-mysql2#using-connection-pools) to manage database connections can reduce the performance overhead caused by frequently establishing and destroying connections. -- To avoid SQL injection, it is recommended to use [prepared statements](https://github.com/sidorares/node-mysql2#using-prepared-statements). +- Using [connection pools](https://sidorares.github.io/node-mysql2/docs#using-connection-pools) to manage database connections can reduce the performance overhead caused by frequently establishing and destroying connections. +- To avoid SQL injection, it is recommended to use [prepared statements](https://sidorares.github.io/node-mysql2/docs#using-prepared-statements). - In scenarios where there are not many complex SQL statements involved, using ORM frameworks like [Sequelize](https://sequelize.org/), [TypeORM](https://typeorm.io/), or [Prisma](https://www.prisma.io/) can greatly improve development efficiency. - It is recommended to enable the `supportBigNumbers: true` option when dealing with big numbers (`BIGINT` and `DECIMAL` columns) in the database. - It is recommended to enable the `enableKeepAlive: true` option to avoid socket error `read ECONNRESET` due to network problems. (Related issue: [sidorares/node-mysql2#683](https://github.com/sidorares/node-mysql2/issues/683)) From 3ff62d5b00a913a40a452079594967b235a6c095 Mon Sep 17 00:00:00 2001 From: lilin90 Date: Fri, 18 Sep 2026 14:38:39 +0800 Subject: [PATCH 5/5] Update node-mysql2 docs link Replace the node-mysql2 GitHub README link in the Node.js + mysql2 sample app guide with the direct official documentation URL for clearer navigation to driver usage docs. --- develop/dev-guide-sample-application-nodejs-mysql2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/develop/dev-guide-sample-application-nodejs-mysql2.md b/develop/dev-guide-sample-application-nodejs-mysql2.md index e11b05fb2312a..af48ebdf3dd6f 100644 --- a/develop/dev-guide-sample-application-nodejs-mysql2.md +++ b/develop/dev-guide-sample-application-nodejs-mysql2.md @@ -305,7 +305,7 @@ For more information, refer to [Delete data](/develop/dev-guide-delete-data.md). ## Next steps -- Learn more usage of node-mysql2 driver from [the documentation of node-mysql2](https://github.com/sidorares/node-mysql2#readme). +- Learn more usage of node-mysql2 driver from [the documentation of node-mysql2](https://sidorares.github.io/node-mysql2/docs/documentation). - Learn the best practices for TiDB application development with the chapters in the [Developer guide](/develop/dev-guide-overview.md), such as: [Insert data](/develop/dev-guide-insert-data.md), [Update data](/develop/dev-guide-update-data.md), [Delete data](/develop/dev-guide-delete-data.md), [Query data](/develop/dev-guide-get-data-from-single-table.md), [Transactions](/develop/dev-guide-transaction-overview.md), [SQL performance optimization](/develop/dev-guide-optimize-sql-overview.md). - Learn through the professional [TiDB developer courses](https://www.pingcap.com/education/) and earn [TiDB certifications](https://www.pingcap.com/education/certification/) after passing the exam.