From bf7efa4b0b3ed2258df4ac7765f21c7b6cf945b3 Mon Sep 17 00:00:00 2001 From: qiancai Date: Fri, 15 Dec 2023 20:37:38 +0800 Subject: [PATCH 1/3] Update foreign-key.md --- foreign-key.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/foreign-key.md b/foreign-key.md index 157d7e6d035b8..2ea480ab70d36 100644 --- a/foreign-key.md +++ b/foreign-key.md @@ -10,7 +10,7 @@ Starting from v6.6.0, TiDB supports the foreign key feature, which allows cross- > **Warning:** > > - Currently, the foreign key feature is experimental. It is not recommended that you use it in production environments. This feature might be changed or removed without prior notice. If you find a bug, you can report an [issue](https://github.com/pingcap/tidb/issues) on GitHub. -> - The foreign key feature is usually used for providing integrity and consistency constraint checks for data in small or medium volumes. However, for large data volumes in a distributed database system, the use of foreign keys might lead to serious performance issues and could have unpredictable effects on the system. If you plan to use foreign keys, conduct thorough validation first and use them with caution. +> - The foreign key feature is typically employed to enforce referential integrity constraint checks. It might introduce performance degradation, so it is recommended to conduct thorough testing before using it in performance-sensitive scenarios. The foreign key is defined in the child table. The syntax is as follows: From 243658f635382ccef0b2549f1d3238a185d5d3e2 Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Fri, 15 Dec 2023 21:12:16 +0800 Subject: [PATCH 2/3] Update foreign-key.md --- foreign-key.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/foreign-key.md b/foreign-key.md index 2ea480ab70d36..b3e0f798f76c1 100644 --- a/foreign-key.md +++ b/foreign-key.md @@ -10,7 +10,7 @@ Starting from v6.6.0, TiDB supports the foreign key feature, which allows cross- > **Warning:** > > - Currently, the foreign key feature is experimental. It is not recommended that you use it in production environments. This feature might be changed or removed without prior notice. If you find a bug, you can report an [issue](https://github.com/pingcap/tidb/issues) on GitHub. -> - The foreign key feature is typically employed to enforce referential integrity constraint checks. It might introduce performance degradation, so it is recommended to conduct thorough testing before using it in performance-sensitive scenarios. +> - The foreign key feature is typically employed to enforce [referential integrity](https://en.wikipedia.org/wiki/Referential_integrity) constraint checks. It might introduce performance degradation, so it is recommended to conduct thorough testing before using it in performance-sensitive scenarios. The foreign key is defined in the child table. The syntax is as follows: From d0705586764e5c2b20eb43457c393bbc37a35d58 Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Mon, 18 Dec 2023 17:57:36 +0800 Subject: [PATCH 3/3] Update foreign-key.md Co-authored-by: xixirangrang --- foreign-key.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/foreign-key.md b/foreign-key.md index b3e0f798f76c1..8ddfe2fd39b9a 100644 --- a/foreign-key.md +++ b/foreign-key.md @@ -10,7 +10,7 @@ Starting from v6.6.0, TiDB supports the foreign key feature, which allows cross- > **Warning:** > > - Currently, the foreign key feature is experimental. It is not recommended that you use it in production environments. This feature might be changed or removed without prior notice. If you find a bug, you can report an [issue](https://github.com/pingcap/tidb/issues) on GitHub. -> - The foreign key feature is typically employed to enforce [referential integrity](https://en.wikipedia.org/wiki/Referential_integrity) constraint checks. It might introduce performance degradation, so it is recommended to conduct thorough testing before using it in performance-sensitive scenarios. +> - The foreign key feature is typically employed to enforce [referential integrity](https://en.wikipedia.org/wiki/Referential_integrity) constraint checks. It might cause performance degradation, so it is recommended to conduct thorough testing before using it in performance-sensitive scenarios. The foreign key is defined in the child table. The syntax is as follows: