Skip to content

Parser rejects column aliases that Snowflake accepts #1607

Closed

Description

@yoavcloud

For example:
SELECT cluster FROM tbl --> accepted by both Snowflake and the parser
SELECT col cluster FROM tbl --> accepted by Snowflake but not by the parser
SELECT col col_alias FROM tbl --> accepted by both Snowflake and the parser
SELECT col AS cluster FROM tbl --> accepted by both Snowflake and the parser (this one really bakes my noodle...)

Activity

  1. yoavcloud commented on Dec 26, 2024

    @yoavcloud
    ContributorAuthor

    The underlying issue here is that when a column alias is provided implicitly, i.e. without the use of the AS keyword, the parser has to decide if the next word after a column ident is an alias or the beginning of some other construct that should be parsed differently.

    For example:
    SELECT 1 LIMIT on Snowflake produces a result set with one column named limit, but the statement SELECT 1 LIMIT 5 produces a result set with one column named 1 (the limit is parsed as a limit on the number of rows in the result set).

    A possible solution is to make this decision more accurate. Instead of looking at just the next word, the parser should look further ahead to identify constructs that should not be parsed as an alias.

  2. iffyio commented on Feb 9, 2025

    @iffyio
    Contributor

    Done in #1632

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions