diff --git a/sql/mysql-compatibility.md b/sql/mysql-compatibility.md
index 0566654c9887e..99bb718198f12 100644
--- a/sql/mysql-compatibility.md
+++ b/sql/mysql-compatibility.md
@@ -15,7 +15,6 @@ However, in TiDB, the following MySQL features are not supported for the time be
 ## Unsupported features
 
 + Stored procedures and functions
-+ Views
 + Triggers
 + Events
 + User-defined functions
@@ -155,6 +154,10 @@ Due to its distributed nature, workloads that are single-threaded may perform wo
 
     When TiDB is in the execution of loading data, by default, a record with 20,000 rows of data is seen as a transaction for persistent storage. If a load data operation inserts more than 20,000 rows, it will be divided into multiple transactions to commit. If an error occurs in one transaction, this transaction in process will not be committed. However, transactions before that are committed successfully. In this case, a part of the load data operation is successfully inserted, and the rest of the data insertion fails. But MySQL treats a load data operation as a transaction, one error leads to the failure of the entire load data operation.
     
+### Views
+
+Views in TiDB are currently non-insertable and non-updatable. We plan to add this functionality at a later date.
+
 ### Storage engines
 
 For compatibility reasons, TiDB supports the syntax to create tables with alternative storage engines. Metadata commands describe tables as being of engine InnoDB: