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

miss "subquery returns more than 1 row" check when MaxChunkSize=1 #7333

Closed
lysu opened this issue Aug 9, 2018 · 3 comments
Closed

miss "subquery returns more than 1 row" check when MaxChunkSize=1 #7333

lysu opened this issue Aug 9, 2018 · 3 comments
Assignees
Labels
sig/execution SIG execution type/bug The issue is confirmed as a bug.

Comments

@lysu
Copy link
Contributor

lysu commented Aug 9, 2018

This issue will be fixed with #7141

  1. What did you do?
create table t(id int primary key, v int);
insert into t values(1, 1), (2, 2), (3, 3);
set @@tidb_max_chunk_size=1;
select (select t.id from t where t.id = t.v and t.v != s.id) from t s;
  1. What did you expect to see?
ERROR 1105 (HY000): subquery returns more than 1 row
  1. What did you see instead?
+-------------------------------------------------------+
| (select t.id from t where t.id = t.v and t.v != s.id) |
+-------------------------------------------------------+
|                                                     2 |
|                                                     1 |
|                                                     1 |
+-------------------------------------------------------+
3 rows in set (0.01 sec)

  1. What version of TiDB are you using (tidb-server -V or run select tidb_version(); on TiDB)?
Release Version: None
Git Commit Hash: None
Git Branch: None
UTC Build Time: None
GoVersion: None
Race Enabled: false
TiKV Min Version: 2.1.0-alpha.1-ff3dd160846b7d1aed9079c389fc188f7f5ea13e
@lysu lysu added the type/bug The issue is confirmed as a bug. label Aug 9, 2018
@lysu lysu self-assigned this Aug 9, 2018
@zz-jason
Copy link
Member

zz-jason commented Aug 9, 2018

@lysu We should fix this issue in an individual PR and cherrypick that PR to release-2.0

@zz-jason zz-jason added the sig/execution SIG execution label Aug 9, 2018
@lysu
Copy link
Contributor Author

lysu commented Aug 9, 2018

@zz-jason ok~

@lysu
Copy link
Contributor Author

lysu commented Aug 29, 2018

fixed by #7375

@lysu lysu closed this as completed Aug 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/execution SIG execution type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

2 participants