fix statement summary table descriptions and add warning message of d…

…rop table (#13088) (#13125)
pingcap · Apr 4, 2023 · 78c093b · 78c093b
1 parent 297f4bf
commit 78c093b
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 4 deletions.
diff --git a/sql-statements/sql-statement-drop-table.md b/sql-statements/sql-statement-drop-table.md
@@ -43,8 +43,17 @@ Query OK, 0 rows affected (0.22 sec)
 
 mysql> DROP TABLE table_not_exists;
 ERROR 1051 (42S02): Unknown table 'test.table_not_exists'
+
 mysql> DROP TABLE IF EXISTS table_not_exists;
-Query OK, 0 rows affected (0.01 sec)
+Query OK, 0 rows affected, 1 warning (0.01 sec)
+
+mysql> SHOW WARNINGS;
++-------+------+---------------------------------------+
+| Level | Code | Message                               |
++-------+------+---------------------------------------+
+| Note  | 1051 | Unknown table 'test.table_not_exists' |
++-------+------+---------------------------------------+
+1 row in set (0.01 sec)
 
 mysql> CREATE VIEW v1 AS SELECT 1;
 Query OK, 0 rows affected (0.10 sec)
@@ -55,8 +64,7 @@ Query OK, 0 rows affected (0.23 sec)
 
 ## MySQL compatibility
 
-* Dropping a table with `IF EXISTS` does not return a warning when attempting to drop a table that does not exist. [Issue #7867](https://github.com/pingcap/tidb/issues/7867)
-* Currently `RESTRICT` and `CASCADE` are only supported syntactically.
+Currently, `RESTRICT` and `CASCADE` are only supported syntactically.
 
 ## See also
 

diff --git a/statement-summary-tables.md b/statement-summary-tables.md
@@ -107,7 +107,7 @@ The `statements_summary_evicted` table is updated only when a SQL record is evic
 
 The `statements_summary`, `statements_summary_history`, and `statements_summary_evicted` tables only show the statement summary of a single TiDB server. To query the data of the entire cluster, you need to query the `cluster_statements_summary`, `cluster_statements_summary_history`, or `cluster_statements_summary_evicted` tables.
 
-`cluster_statements_summary` displays the `statements_summary` data of each TiDB server. `cluster_statements_summary_history` displays the `statements_summary_history` data of each TiDB server. `cluster_statements_summary_evicted` displays the `statements_summary_evicted` data of each TiDB server. These tables use the `INSTANCE` field to represent the address of the TiDB server. The other fields are the same as those in `statements_summary`.
+`cluster_statements_summary` displays the `statements_summary` data of each TiDB server. `cluster_statements_summary_history` displays the `statements_summary_history` data of each TiDB server. `cluster_statements_summary_evicted` displays the `statements_summary_evicted` data of each TiDB server. These tables use the `INSTANCE` field to represent the address of the TiDB server. The other fields are the same as those in `statements_summary`, `statements_summary_history`, and `statements_summary_evicted`.
 
 ## Parameter configuration