Problems encountered when using the right join field function and monocular operators together
- 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)
Table building statement:
CREATE TABLE t0(c0 BOOL ZEROFILL DEFAULT false , PRIMARY KEY(c0)) AUTO_ID_CACHE 100 ;
CREATE TABLE t1(c0 NUMERIC UNSIGNED ZEROFILL ) AUTO_ID_CACHE 100 ;
ALTER TABLE t0 ORDER BY c0;
TRUNCATE t0;
ANALYZE TABLE t0;
UPDATE t0 SET c0='E^3' WHERE t0.c0;
UPDATE t0 SET c0=((1921384943)NOT LIKE(LOG2('0')));
INSERT IGNORE INTO t0 VALUES (0.9291865158593959), (''), (-956624558) ON DUPLICATE KEY UPDATE c0=t0.c0;
Statement that triggers a bug:
SELECT t1.c0,t0.c0 FROM t1 RIGHT JOIN t0 ON t1.c0 WHERE FIELD(0, ((-1128017836)AND(((((t1.c0)<(736467147)))<('')))), (((NOT (((t0.c0) IS NULL))))&(((0.741134455662442)>(t0.c0)))));
### 2. What did you expect to see? (Required)
Return a piece of data:[null,1]
### 3. What did you see instead (Required)
No data returned
### 4. What is your TiDB version? (Required)
6.6.0
Contributor guide
Assessment
This issue has not been assessed yet.