-
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
Can't find column XXX in schema Column #41986
Labels
affects-6.1
affects-6.5
affects-7.0
affects-7.1
report/community
The community has encountered this bug.
severity/major
sig/planner
SIG: Planner
type/bug
The issue is confirmed as a bug.
Comments
Maybe same as #41957, PTAL @xuyifangreeneyes |
ti-chi-bot
added
may-affects-4.0
This bug maybe affects 4.0.x versions.
may-affects-5.0
This bug maybe affects 5.0.x versions.
may-affects-5.1
This bug maybe affects 5.1.x versions.
may-affects-5.2
This bug maybe affects 5.2.x versions.
may-affects-5.3
This bug maybe affects 5.3.x versions.
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-6.1
may-affects-6.5
labels
Mar 8, 2023
12 tasks
AilinKid
added
affects-6.1
affects-6.5
and removed
may-affects-4.0
This bug maybe affects 4.0.x versions.
may-affects-5.1
This bug maybe affects 5.1.x versions.
may-affects-5.2
This bug maybe affects 5.2.x versions.
may-affects-5.3
This bug maybe affects 5.3.x versions.
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-5.0
This bug maybe affects 5.0.x versions.
may-affects-6.1
may-affects-6.5
labels
Aug 25, 2023
Merged
12 tasks
/found community |
ti-chi-bot
bot
added
the
report/community
The community has encountered this bug.
label
Jun 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-6.1
affects-6.5
affects-7.0
affects-7.1
report/community
The community has encountered this bug.
severity/major
sig/planner
SIG: Planner
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
CREATE TABLE poi_clearing_time_topic (
effective_date datetime DEFAULT NULL ,
clearing_time int(11) DEFAULT NULL
);
SELECT
GROUP_CONCAT(stlmnt_hour order by effective_date DESC)
-- GROUP_CONCAT(stlmnt_hour )
FROM
(
SELECT
(COALESCE(pct.clearing_time, 0)/3600000) AS stlmnt_hour
,COALESCE(pct.effective_date, '1970-01-01 08:00:00') AS effective_date
FROM
poi_clearing_time_topic pct
ORDER BY
pct.effective_date DESC
) a;
2. What did you expect to see? (Required)
no error.
3. What did you see instead (Required)
the sql returns error: Can't find column a.effective_date in schema Column: [stlmnt_hour,effective_date,test.pct.effective_date] Unique key: []
4. What is your TiDB version? (Required)
3.0, 5.0, 6.1 (maybe all versions)
The text was updated successfully, but these errors were encountered: