Skip to content

The new analyzer has a different behaviour with join/using when join-columns are renamed in the SELECT #56814

@den-crane

Description

@den-crane

https://fiddle.clickhouse.com/8f0a999f-6799-4d4e-b5cb-1d92608bee22

The new behaviour is more SQL-ansi. It uses column names from the tables not from SELECT section.
I have such queries in my production and they don't use a subquery for the left table, because in case of distributed tables it moves join to the initiator. I am going to rewrite all such queries to use ON instead of USING.

But it maybe unexpected for other users. Maybe such queries should throw an exception? Which can be fixed by the setting?

@vdimir @kitaisreal

Metadata

Metadata

Assignees

Labels

analyzerIssues and pull-requests related to new analyzerquestionQuestion?

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions