This can also be triggered by:

> select * from x where exists(select b from no_such_table);
query error: qualified name "x.b" not found

That error might be a red herring, since it is also produced by:

> select no_such_col from x;
query error: qualified name "x.no_such_col" not found

There is also:

> select * from x where exists(select a from no_such_table);
+---+
| a |
+---+
+---+

Where it successfully returns a result when a bogus table is specified.

Edit: the table x above was empty when I ran that query. When it has a row, the error changes to:

query error: sql/parser/eval.go:1049: unhandled type *parser.Subquery

I don't understand how it could be a red herring.

Assigning to @petermattis because I couldn't figure this out (and neither could @mjibson).

Ok, I'll take a look.

@mjibson @tamird PTAL

The error message was coming from scanNode.resolveQNames and was occurring because ExistsExpr.Walk was skipping over the Subquery node and walking the internal Subquery.Select.

LGTM. You can git commit --amend --reset-author to make yourself the author of this commit.

LGTM

Review status: 0 of 6 files reviewed at latest revision, 4 unresolved discussions.

sql/parser/eval.go, line 878 [r2] (raw file):
handle -> handled

sql/parser/eval.go, line 1081 [r2] (raw file):
handle -> handled

sql/subquery.go, line 73 [r2] (raw file):
expression -> expressions
lease -> least

Comments from the review on Reviewable.io

Good grief, I swear my grammar is better than what I demonstrated in this PR.

Review status: 0 of 6 files reviewed at latest revision, 4 unresolved discussions.

Comments from the review on Reviewable.io