-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
planner: don't push down conditions from in subquery with aggregators even though the columns in conditions is not null #13743
Comments
Thanks. // f is empty table.
select 2 in (select null from s) as f; // mysql: null, tidb:0
select 2 in (select s.a from s) as f;// both 0
select 2 in (select s.b from s) as f; // both 0
select 2 in (select 1 from s) as f; // both 0 I try four sql, only the first is wrong. |
@jingyugao |
|
@jingyugao
|
Please edit this comment or add a new comment to complete the following informationNot a bug
Duplicate bug
BugNote: Make Sure that 'component', and 'severity' labels are added 1. Root Cause Analysis (RCA) (optional)2. Symptom (optional)3. All Trigger Conditions (optional)4. Workaround (optional)5. Affected versions6. Fixed versions |
Bug Report
Please answer these questions before submitting your issue. Thanks!
results from MySQL:
Results from TiDB:
The explain results:
The essential problem is :
tidb-server -V
or runselect tidb_version();
on TiDB)?After the master merged with planner:dont push down right condition for anti semi join #12075, there are still errors.
The text was updated successfully, but these errors were encountered: