TiDB does not handle `NO_ZERO_IN_DATE` correctly in `cast`
- Dominant language
- Go
- Stars
- 40.5k
- Forks
- 6.2k
- PR merge metrics
- PR metrics pending
Description
## Bug Report
Please answer these questions before submitting your issue. Thanks!
### 1. Minimal reproduce step (Required)
```
> set @@sql_mode='NO_ZERO_IN_DATE';
> select cast('2022-01-00' as date);
```
### 2. What did you expect to see? (Required)
In Mysql8.0:
```
mysql> set @@sql_mode='NO_ZERO_IN_DATE';
Query OK, 0 rows affected, 1 warning (0.00 sec)
mysql> select cast('2022-01-00' as date);
+----------------------------+
| cast('2022-01-00' as date) |
+----------------------------+
| NULL |
+----------------------------+
1 row in set, 1 warning (0.00 sec)
```
### 3. What did you see instead (Required)
In TiDB:
```
mysql> set @@sql_mode='NO_ZERO_IN_DATE';
Query OK, 0 rows affected (0.00 sec)
mysql> select cast('2022-01-00' as date);
+----------------------------+
| cast('2022-01-00' as date) |
+----------------------------+
| 2022-01-00 |
+----------------------------+
1 row in set (0.00 sec)
```
### 4. What is your TiDB version? (Required)
Contributor guide
Assessment
This issue has not been assessed yet.