Skip to content

select ! should raise an error if it can't exclude #2292

Open
@max-sixty

Description

@max-sixty

What happened?

Currently an invalid select ! is silently ignored

PRQL input

from tracks
select ![milliseconds,bytes]

SQL output

SELECT
  *
FROM
  tracks

-- Generated by PRQL compiler version:0.6.1 (https://prql-lang.org)

Expected SQL output

Error: we don't know the columns prior to `select ![milliseconds,bytes]`, and we're not using a target that natively supports excluding columns.

MVCE confirmation

  • Minimal example
  • New issue

Anything else?

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions