From b27faff3310b5d625443a81c64b8b3adc44c81b8 Mon Sep 17 00:00:00 2001 From: Morgan Tocker Date: Mon, 14 Jan 2019 19:02:52 -0700 Subject: [PATCH] sql: allow_invalid_dates is now supported via https://github.com/pingcap/tidb/pull/9027 --- sql/mysql-compatibility.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/sql/mysql-compatibility.md b/sql/mysql-compatibility.md index ff61c1dd7a6d0..012a4a7844a07 100644 --- a/sql/mysql-compatibility.md +++ b/sql/mysql-compatibility.md @@ -175,10 +175,9 @@ Architecturally, TiDB does support a similar storage engine abstraction to MySQL TiDB supports **all of the SQL modes** from MySQL 5.7 with minor exceptions: -1. The `ALLOW_INVALID_DATES` mode is not yet supported. See [TiDB #8263](https://github.com/pingcap/tidb/issues/8263). -2. The compatibility modes deprecated in MySQL 5.7 and removed in MySQL 8.0 are not supported (such as `ORACLE`, `POSTGRESQL` etc). -3. The mode `ONLY_FULL_GROUP_BY` has minor [semantic differences](../sql/aggregate-group-by-functions.md#differences-from-mysql) to MySQL 5.7, which we plan to address in the future. -4. The SQL modes `NO_DIR_IN_CREATE` and `NO_ENGINE_SUBSTITUTION` are supported for compatibility, but are not applicable to TiDB. +1. The compatibility modes deprecated in MySQL 5.7 and removed in MySQL 8.0 are not supported (such as `ORACLE`, `POSTGRESQL` etc). +2. The mode `ONLY_FULL_GROUP_BY` has minor [semantic differences](../sql/aggregate-group-by-functions.md#differences-from-mysql) to MySQL 5.7, which we plan to address in the future. +3. The SQL modes `NO_DIR_IN_CREATE` and `NO_ENGINE_SUBSTITUTION` are supported for compatibility, but are not applicable to TiDB. ### EXPLAIN