pingcap / pingcap/tidb

Problems encountered when using natural right join and dataformat functions together

Open
#42,378 0 comments 0 reactions 0 assignees View on GitHub
affects-8.5 may-affects-5.4 may-affects-6.1 may-affects-6.5 may-affects-7.1 may-affects-7.5 may-affects-8.1 severity/minor sig/planner 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)
Table building statement:
CREATE TABLE t0(c0 CHAR UNIQUE ) AUTO_ID_CACHE 100 ;
CREATE TABLE t1 LIKE t0;
ALTER TABLE t0 CHANGE c0 c0 CHAR NOT NULL ;
ALTER TABLE t0 ORDER BY c0 ASC;
set @@tidb_hashagg_partial_concurrency=77;
ALTER TABLE t1 CHANGE c0 c0 CHAR NOT NULL ;
TRUNCATE t1;
ALTER TABLE t0 MODIFY c0 NUMERIC;
INSERT IGNORE INTO t0(c0) VALUES (NULL);
ALTER TABLE t0 DISABLE KEYS;

Statement that triggers a bug:
SELECT t0.c0,t1.c0 FROM t1 NATURAL RIGHT JOIN t0 WHERE (NOT (DATE_FORMAT(false, (CASE -2095575353 WHEN t1.c0 THEN 0.050125161000388774 ELSE false END ))));

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

### 3. What did you see instead (Required)
Return a piece of data [null,null]

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

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.