Skip to content

Unable to provide explicit precedence on combinations such as UNION and INTERSECT #369

@alexmg

Description

@alexmg

It does not seem to be possible to be explicit about the precedence when applying more than one combination.

In the example below, without the additional parentheses the INTERSECT will take precedence over the UNION.

(SELECT 1

UNION

SELECT 2)

INTERSECT

SELECT 2

Is there a way to workaround this issue and add parentheses as needed to enforce the desired precedence?

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