From 8682bd7898aba383744e41b2faa21a932525307b Mon Sep 17 00:00:00 2001 From: Morgan Tocker Date: Wed, 1 Sep 2021 18:28:16 -0600 Subject: [PATCH 1/2] system-variables: improve noop functions warning --- system-variables.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/system-variables.md b/system-variables.md index a89e73616c4d7..feb7ece4f05fd 100644 --- a/system-variables.md +++ b/system-variables.md @@ -595,9 +595,9 @@ Constraint checking is always performed in place for pessimistic transactions (d * `START TRANSACTION READ ONLY` and `SET TRANSACTION READ ONLY` syntax * The `tx_read_only`, `transaction_read_only`, `offline_mode`, `super_read_only` and `read_only` system variables -> **Note:** +> **Warning:** > -> Only the default value of `OFF` can be considered safe. Setting `tidb_enable_noop_functions=1` might lead to unexpected behaviors in your application, because it permits TiDB to ignore certain syntax without providing an error. +> Only the default value of `OFF` can be considered safe. Setting `tidb_enable_noop_functions=1` might lead to unexpected behaviors in your application, because it permits TiDB to ignore certain syntax without providing an error. For example, the syntax `START TRANSACTION READ ONLY` will be permitted, but transactions will remain in read-write mode. ### tidb_enable_parallel_apply New in v5.0 From 255d834418a3f663aa117218ad5348224ae4a8f4 Mon Sep 17 00:00:00 2001 From: Morgan Tocker Date: Wed, 8 Sep 2021 09:15:52 -0600 Subject: [PATCH 2/2] Update system-variables.md Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com> --- system-variables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/system-variables.md b/system-variables.md index feb7ece4f05fd..5c451229f6d70 100644 --- a/system-variables.md +++ b/system-variables.md @@ -597,7 +597,7 @@ Constraint checking is always performed in place for pessimistic transactions (d > **Warning:** > -> Only the default value of `OFF` can be considered safe. Setting `tidb_enable_noop_functions=1` might lead to unexpected behaviors in your application, because it permits TiDB to ignore certain syntax without providing an error. For example, the syntax `START TRANSACTION READ ONLY` will be permitted, but transactions will remain in read-write mode. +> Only the default value of `OFF` can be considered safe. Setting `tidb_enable_noop_functions=1` might lead to unexpected behaviors in your application, because it permits TiDB to ignore certain syntax without providing an error. For example, the syntax `START TRANSACTION READ ONLY` is permitted, but the transaction remains in read-write mode. ### tidb_enable_parallel_apply New in v5.0