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

Table aliases not supported? #28

Open
tuulos opened this issue Mar 12, 2018 · 1 comment
Open

Table aliases not supported? #28

tuulos opened this issue Mar 12, 2018 · 1 comment

Comments

@tuulos
Copy link

tuulos commented Mar 12, 2018

Are table aliases like a in FROM some_table a supported?

For example

> demoAllAnalyses "select a.x from some_table a"
Tables accessed:
    public.some_table
Columns accessed by clause:
    <unknown>.a.x       SELECT
Joins:
    no joins
Table lineage:
    no tables modified

In this case, is it possible to resolve <unknown> to some_table?

@h4v0kh3l1
Copy link
Contributor

Hey @tuulos ,

Yes, we intend to support resolving aliases in column access, we have table alias resolution but it looks like this particular case slipped under the radar.

This example provided will have different behavior, since some_table doesn't exist in the catalog, and the resolve step reverts to defaulting. However, if you swap in foo, which is defined in the demo catalog, you'll get the same behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants