From 84e998922fac5d45b040ce913e744d8e7cec6cad Mon Sep 17 00:00:00 2001 From: qw4990 Date: Wed, 8 Jan 2025 17:07:38 +0800 Subject: [PATCH] fixup --- sql-plan-cache.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/sql-plan-cache.md b/sql-plan-cache.md index 4db5f2c881dad..e1373d1225070 100644 --- a/sql-plan-cache.md +++ b/sql-plan-cache.md @@ -343,8 +343,6 @@ After you enable this feature, the optimizer quickly evaluates the query. If it To reduce the syntax parsing cost of SQL statements, it is recommended that you run `prepare stmt` once, then `execute stmt` multiple times before running `deallocate prepare`: -{{< copyable "sql" >}} - ```sql MySQL [test]> prepare stmt from '...'; -- Prepare once MySQL [test]> execute stmt using ...; -- Execute once @@ -355,8 +353,6 @@ MySQL [test]> deallocate prepare stmt; -- Release the prepared statement In real practice, you may be used to running `deallocate prepare` each time after running `execute stmt`, as shown below: -{{< copyable "sql" >}} - ```sql MySQL [test]> prepare stmt from '...'; -- Prepare once MySQL [test]> execute stmt using ...;