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

Invalid column error not completely fixed #3733

Closed
YuanchengJiang opened this issue Sep 12, 2023 · 0 comments · Fixed by #3912
Closed

Invalid column error not completely fixed #3733

YuanchengJiang opened this issue Sep 12, 2023 · 0 comments · Fixed by #3912
Labels
Bug Incorrect or unexpected behavior SQL Issues or changes relating to SQL execution

Comments

@YuanchengJiang
Copy link

Describe the bug

Related issues: #3670 #3619 #3595

Invalid column: T2.event
LINE 1: ... JOIN (SELECT * FROM telemetry) as T2 ON T1.event<T2.event J...

To reproduce

Run:

SELECT count(*) FROM telemetry as T1 JOIN (SELECT * FROM telemetry) as T2 ON T1.event<T2.event JOIN telemetry as T3 ON T2.created=T3.created

If you remove the subquery or one less JOIN, it works:

SELECT count(*) FROM telemetry as T1 JOIN telemetry as T2 ON T1.event<T2.event JOIN telemetry as T3 ON T2.created=T3.created
SELECT count(*) FROM telemetry as T1 JOIN (SELECT * FROM telemetry) as T2 ON T1.event<T2.event

Expected Behavior

Valid query should return results

Environment

- **QuestDB version**: 7.3.2

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Incorrect or unexpected behavior SQL Issues or changes relating to SQL execution
Projects
None yet
2 participants