Skip to content

Resolving incorrectly fails with AmbiguousColumn #56

@lukas-mi

Description

@lukas-mi

Hi, seems like resolver gets confused about the context used for resolution when trying to resolve columns in nested queries and fails with AmbiguousColumn error, e.g.: select a from demo.foo where a in (select a from demo.foo);

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions