We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Summary
mysql> insert into t1 values(1), (2), (2), (3); Query OK, 4 rows affected (0.38 sec) mysql> insert into t2 values(1), (2), (3); Query OK, 3 rows affected (0.25 sec) mysql> select count(distinct a) over (partition by (select b from t2)) from t1; +-----------+ | count(_1) | +-----------+ | 3 | +-----------+ 1 row in set (0.09 sec) Read 4 rows, 17.00 B in 0.048 sec., 83.91 rows/sec., 356.61 B/sec.
The text was updated successfully, but these errors were encountered:
pg: error: more than one row returned by a subquery used as an expression
mysql: error: ER_SUBQUERY_NO_1_ROW: Subquery returns more than 1 row
sqlite:
4 4 4 4
Sorry, something went wrong.
Which behavior should we follow? Open to discuss.
I think pg is better. It's more clear.
Snowflake:
xudong963
Successfully merging a pull request may close this issue.
Summary
The text was updated successfully, but these errors were encountered: