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

Ifnull enum type with not null flag has different result #24944

Closed
wshwsh12 opened this issue May 28, 2021 · 2 comments · Fixed by #25110
Closed

Ifnull enum type with not null flag has different result #24944

wshwsh12 opened this issue May 28, 2021 · 2 comments · Fixed by #25110
Labels
severity/critical sig/execution SIG execution type/bug The issue is confirmed as a bug.

Comments

@wshwsh12
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

drop table if exists t,t2;
create table t(e enum("a","b","c") not null, b int);
create table t2(e enum("a","b","c"), b int);
insert into t values(1,1);
insert into t2 values(1,1);

select * from t where ifnull(e,b);
select * from t2 where ifnull(e,b);

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

Same result.

3. What did you see instead (Required)

[tidb]> select * from t where ifnull(e,b);
+---+------+
| e | b    |
+---+------+
| a |    1 |
+---+------+
1 row in set (0.001 sec)

[tidb]> select * from t2 where ifnull(e,b);
Empty set, 1 warning (0.001 sec)

4. What is your TiDB version? (Required)

master, v5.0,v4.0

@wshwsh12 wshwsh12 added the type/bug The issue is confirmed as a bug. label May 28, 2021
@wshwsh12 wshwsh12 changed the title Ifnull enum type with index/non-index has different result Ifnull enum type with not null flag has different result May 28, 2021
@guo-shaoge
Copy link
Collaborator

We directly rewrite ifnull to its argument if first argument got not null flag. Check here

@ti-srebot
Copy link
Contributor

Please edit this comment or add a new comment to complete the following information

Not a bug

  1. Remove the 'type/bug' label
  2. Add notes to indicate why it is not a bug

Duplicate bug

  1. Add the 'type/duplicate' label
  2. Add the link to the original bug

Bug

Note: Make Sure that 'component', and 'severity' labels are added
Example for how to fill out the template: #20100

1. Root Cause Analysis (RCA) (optional)

2. Symptom (optional)

3. All Trigger Conditions (optional)

4. Workaround (optional)

5. Affected versions

6. Fixed versions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/critical sig/execution SIG execution type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants