Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When truncate is NULL, 1 BETWEEN truncate() AND 1 outputs unexpected 1 #57608

Open
r33s3n6 opened this issue Nov 21, 2024 · 0 comments
Open

When truncate is NULL, 1 BETWEEN truncate() AND 1 outputs unexpected 1 #57608

r33s3n6 opened this issue Nov 21, 2024 · 0 comments
Labels
type/bug The issue is confirmed as a bug.

Comments

@r33s3n6
Copy link

r33s3n6 commented Nov 21, 2024

1. Minimal reproduce step (Required)

create table t1 ( c1 int primary key);
insert into t1 (c1) values (1), (2), (3), (4), (5), (6), (7), (11), (12), (13), (14), (15), (16), (17), (21), (22), (23), (24), (25), (26), (27), (116), (127), (121), (122), (113), (214), (251), (261), (217), (91), (92), (39), (94), (95), (69), (79), (191), (129);

create view v2 as select 0 as q2 from t1;

select distinct
  1 between NULL and 1 as w0, 
  truncate(1, (cast(ref_1.q2 as unsigned) % 0)) as w1,
  (1 between truncate(1, (cast(ref_1.q2 as unsigned) % 0)) and 1) as w2
from 
  (v2 as ref_0 inner join v2 as ref_1 on (1=1))
;

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

The third column should not have 1
in TiDB with unistore:

mysql> select distinct   1 between NULL and 1 as w0,    truncate(1, (cast(ref_1.q2 as unsigned) % 0)) as w1,   (1
between truncate(1, (cast(ref_1.q2 as unsigned) % 0)) and 1) as w2 from    (v2 as ref_0 inner join v2 as ref_1 on
(1=1));
+------+------+------+
| w0   | w1   | w2   |
+------+------+------+
| NULL | NULL | NULL |
+------+------+------+
1 row in set, 3042 warnings (0.05 sec)

3. What did you see instead (Required)

in TiDB with TiKV

mysql> select distinct
    ->   1 between NULL and 1 as w0, 
    ->   truncate(1, (cast(ref_1.q2 as unsigned) % 0)) as w1,
    ->   (1 between truncate(1, (cast(ref_1.q2 as unsigned) % 0)) and 1) as w2
    -> from 
    ->   (v2 as ref_0 inner join v2 as ref_1 on (1=1))
    -> ;
+------+------+------+
| w0   | w1   | w2   |
+------+------+------+
| NULL | NULL |    1 |
| NULL | NULL | NULL |
+------+------+------+
2 rows in set, 1880 warnings (0.00 sec)

4. What is your TiDB version? (Required)

Release Version: v8.5.0-alpha-184-g1c059a1216
Edition: Community
Git Commit Hash: 1c059a1216db711e2cb56ea9f3d1ad8c23db6327
Git Branch: HEAD
UTC Build Time: 2024-11-21 04:56:22
GoVersion: go1.23.3
Race Enabled: false
Check Table Before Drop: false
Store: tikv

topology:
distributed.yaml:

global:
  user: "tidb"
  ssh_port: 22
  deploy_dir: "/tidb-deploy"
  data_dir: "/tidb-data"

tidb_servers:
  - host: 10.0.2.81

pd_servers:
  - host: 10.0.2.82

tikv_servers:
  - host: 10.0.2.83

about us

We are the BASS team from the School of Cyber Science and Technology at Beihang University. Our main focus is on system software security, operating systems, and program analysis research, as well as the development of automated program testing frameworks for detecting software defects. Using our self-developed database vulnerability testing tool, we have identified the above-mentioned vulnerabilities in TiDB that may lead to database logic error.

@r33s3n6 r33s3n6 added the type/bug The issue is confirmed as a bug. label Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

1 participant