From 4c0eb203e4a801f8a369dba471cb3ab50b2d315c Mon Sep 17 00:00:00 2001 From: Lilian Lee Date: Tue, 19 Nov 2024 15:27:40 +0800 Subject: [PATCH] Apply suggestions from code review Co-authored-by: xixirangrang --- develop/dev-guide-sample-application-nodejs-prisma.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/develop/dev-guide-sample-application-nodejs-prisma.md b/develop/dev-guide-sample-application-nodejs-prisma.md index 375f0aa362370..e90fa8ab28d41 100644 --- a/develop/dev-guide-sample-application-nodejs-prisma.md +++ b/develop/dev-guide-sample-application-nodejs-prisma.md @@ -356,7 +356,7 @@ For more information, refer to [Delete data](/develop/dev-guide-delete-data.md). To check [referential integrity](https://en.wikipedia.org/wiki/Referential_integrity?useskin=vector), you can use foreign key constraints or Prisma relation mode: -- [Foreign key](https://docs.pingcap.com/tidb/stable/foreign-key) is a feature supported starting from TiDB v6.6.0, generally available starting from v8.5.0. Foreign keys allow cross-table references of related data, while foreign key constraints ensure the consistency of related data. +- [Foreign key](https://docs.pingcap.com/tidb/stable/foreign-key) is a feature supported starting from TiDB v6.6.0, and generally available starting from v8.5.0. Foreign keys allow cross-table references of related data, while foreign key constraints ensure the consistency of related data. > **Warning:** >