pingcap / pingcap/tidb

The implicit casting rule of `FIELD` is not compatible with MySQL

Open
#59,448 1 comment 0 reactions 0 assignees View on GitHub
component/expression severity/moderate sig/execution type/bug
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)

### 2. What did you expect to see? (Required)

```
mysql> SELECT FIELD('2023-10-01', DATE '2023-10-01');
+----------------------------------------+
| FIELD('2023-10-01', DATE '2023-10-01') |
+----------------------------------------+
| 1 |
+----------------------------------------+
1 row in set (0.02 sec)
```

### 3. What did you see instead (Required)

```
mysql> SELECT FIELD('2023-10-01', DATE '2023-10-01');
+----------------------------------------+
| FIELD('2023-10-01', DATE '2023-10-01') |
+----------------------------------------+
| 0 |
+----------------------------------------+
1 row in set, 1 warning (0.00 sec)

mysql> show warnings;
+---------+------+------------------------------------------------+
| Level | Code | Message |
+---------+------+------------------------------------------------+
| Warning | 1292 | Truncated incorrect DOUBLE value: '2023-10-01' |
+---------+------+------------------------------------------------+
1 row in set (0.00 sec)
```

### 4. What is your TiDB version? (Required)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.