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

sql: error when generate_series is used with scalar-group-by #45843

Open
andy-kimball opened this issue Mar 8, 2020 · 2 comments
Open

sql: error when generate_series is used with scalar-group-by #45843

andy-kimball opened this issue Mar 8, 2020 · 2 comments
Labels
C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. P-3 Issues/test failures with no fix SLA S-3-ux-surprise Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption. T-sql-queries SQL Queries Team

Comments

@andy-kimball
Copy link
Contributor

andy-kimball commented Mar 8, 2020

Repro:

root@:26257/defaultdb> SELECT max(1), generate_series(1,3);
ERROR: column "generate_series" must appear in the GROUP BY clause or be used in an aggregate function

EXPECTED: This should work. PG gives this output:

template1=# SELECT max(1), generate_series(1,3);
 max | generate_series
-----+-----------------
   1 |               1
   1 |               2
   1 |               3

Jira issue: CRDB-5126

@andy-kimball andy-kimball added this to Triage in BACKLOG, NO NEW ISSUES: SQL Optimizer via automation Mar 8, 2020
@awoods187 awoods187 added C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. S-3-ux-surprise Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption. labels Mar 9, 2020
@RaduBerinde RaduBerinde moved this from Triage to Functional issues in BACKLOG, NO NEW ISSUES: SQL Optimizer Apr 18, 2020
@jlinder jlinder added the T-sql-queries SQL Queries Team label Jun 16, 2021
@github-actions
Copy link

We have marked this issue as stale because it has been inactive for
18 months. If this issue is still relevant, removing the stale label
or adding a comment will keep it active. Otherwise, we'll close it in
10 days to keep the issue queue tidy. Thank you for your contribution
to CockroachDB!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 26, 2023
BACKLOG, NO NEW ISSUES: SQL Optimizer automation moved this from Functional issues to Done Sep 26, 2023
@andy-kimball
Copy link
Contributor Author

Still a problem.

@andy-kimball andy-kimball reopened this Sep 26, 2023
BACKLOG, NO NEW ISSUES: SQL Optimizer automation moved this from Done to Triage Sep 26, 2023
@rytaft rytaft removed their assignment Dec 4, 2023
@yuzefovich yuzefovich added the P-3 Issues/test failures with no fix SLA label Dec 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. P-3 Issues/test failures with no fix SLA S-3-ux-surprise Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption. T-sql-queries SQL Queries Team
Projects
Status: Bugs to Fix
Development

No branches or pull requests

5 participants