From 2cd6ece7c71a7b8c97535f8fdd445ecaa2d03fa7 Mon Sep 17 00:00:00 2001 From: Ryosei Sato <132046562+sary8@users.noreply.github.com> Date: Wed, 16 Sep 2026 21:50:56 +0900 Subject: [PATCH 1/4] 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 12bd66854fa81..f40be6588fd42 100644 --- a/develop/dev-guide-sample-application-aws-lambda.md +++ b/develop/dev-guide-sample-application-aws-lambda.md @@ -359,7 +359,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 b36f71a64940d..f5947b222bdfd 100644 --- a/develop/dev-guide-sample-application-nextjs.md +++ b/develop/dev-guide-sample-application-nextjs.md @@ -276,7 +276,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 e794f9b2c3aed05bc470267312ca050277473653 Mon Sep 17 00:00:00 2001 From: Ryosei Sato <132046562+sary8@users.noreply.github.com> Date: Wed, 16 Sep 2026 21:51:16 +0900 Subject: [PATCH 2/4] *: pin the pingcap/tidb source links to the release-6.5 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-6.5 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 6e5cd326c66bf..8bd99397a6d53 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.stats_*`) - 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-6.5/br/pkg/restore/systable_restore.go#L31) When you restore data related to system privilege, note that before restoring data, BR checks whether the system tables in the target cluster are compatible with those in the backup data. "Compatible" means that all the following conditions are met: diff --git a/faq/backup-and-restore-faq.md b/faq/backup-and-restore-faq.md index 7ccbe42555c4f..f52fda8784394 100644 --- a/faq/backup-and-restore-faq.md +++ b/faq/backup-and-restore-faq.md @@ -296,7 +296,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-6.5/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 5620b19722fc8..ab49b9c0b82ba 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-6.5/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 0d6611c7d9abe..8b93b3eaa1a94 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-6.5/br/pkg/lightning). - 6.3.2 Import speed is too slow. From 18ad99b243979775ef79aae9f81c8930448a29ba Mon Sep 17 00:00:00 2001 From: Ryosei Sato <132046562+sary8@users.noreply.github.com> Date: Wed, 16 Sep 2026 21:51:34 +0900 Subject: [PATCH 3/4] 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 ++-- 1 file changed, 2 insertions(+), 2 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) From 2f70b815a66c846d042b44d3df708847107af8cb Mon Sep 17 00:00:00 2001 From: lilin90 Date: Sun, 20 Sep 2026 14:42:41 +0800 Subject: [PATCH 4/4] Update node-mysql2 docs links This change updates the node-mysql2 documentation links in the sample app guides to the current docs site. The affected guides include AWS Lambda, Next.js, and Node.js MySQL2 examples, ensuring the connection pool and prepared statement references point to the correct pages. --- develop/dev-guide-sample-application-aws-lambda.md | 4 ++-- develop/dev-guide-sample-application-nextjs.md | 4 ++-- develop/dev-guide-sample-application-nodejs-mysql2.md | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/develop/dev-guide-sample-application-aws-lambda.md b/develop/dev-guide-sample-application-aws-lambda.md index f40be6588fd42..56e1a7f7f6031 100644 --- a/develop/dev-guide-sample-application-aws-lambda.md +++ b/develop/dev-guide-sample-application-aws-lambda.md @@ -350,8 +350,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. - 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 f5947b222bdfd..46f7c415ad203 100644 --- a/develop/dev-guide-sample-application-nextjs.md +++ b/develop/dev-guide-sample-application-nextjs.md @@ -269,8 +269,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 7ee667547b7eb..c9d9e0da780c9 100644 --- a/develop/dev-guide-sample-application-nodejs-mysql2.md +++ b/develop/dev-guide-sample-application-nodejs-mysql2.md @@ -294,8 +294,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))