-
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
select var_pop(distinct xxx) could successfully execute in TiDB but failed in MySQL #19499
Labels
challenge-program
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
sig/execution
SIG execution
type/compatibility
Comments
/label sig/execution |
SunRunAway
added
type/compatibility
and removed
type/bug
The issue is confirmed as a bug.
labels
Nov 3, 2020
Closed
/pick-up |
Pick up success. |
@hidehalo You did not submit PR within 7 days, so give up automatically. |
/pick-up |
Pick up success. |
Postgres also support |
(for those not following, please check the discussion in pingcap/parser#1116.) |
@hidehalo You did not submit PR within 7 days, so give up automatically. |
tisonkun
added
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
and removed
difficulty/easy
labels
Sep 1, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
challenge-program
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
sig/execution
SIG execution
type/compatibility
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
2. What did you expect to see? (Required)
select var_pop(distinct xxx) failed.
I‘ve refered MySQL docs: link
It seems var_pop/stdev func couldn't contains distinct in it.
3. What did you see instead (Required)
It could execute successfully.
4. What is your TiDB version? (Required)
SIG slack channel
#sig-exec
Score
Mentor
The text was updated successfully, but these errors were encountered: