Skip to content

tobilg/polyglot can be used to support SQL dialects? #5700

Open

Description

@eitsupi

Activity

  1. max-sixty commented on Mar 2, 2026

    @max-sixty
    Member

    interesting!!

    do you know how feasible packaging would be?

  2. eitsupi commented on Mar 3, 2026

    @eitsupi
    MemberAuthor

    I haven't seen anything about the contents yet.

  3. snth commented on Mar 6, 2026

    @snth
    Member

    This is cool. I was aware of sqlglot, but there the issue was that it was Python.

  4. snth commented on Mar 6, 2026

    @snth
    Member

    @eitsupi so you're suggesting that prql-compiler produces ANSI SQL and then polyglot could specialise to the target dialect?

  5. eitsupi commented on Mar 6, 2026

    @eitsupi
    MemberAuthor

    In fact, I'm not sure how much it will be usable.
    For example, something like DuckDB's exclude can be translated directly from PRQL, but I expect that it will become unsupportable once it goes through ANSI SQL.

  6. snth commented on Mar 6, 2026

    @snth
    Member

    Good point. So I think Substrait is still the best option as compilation target and then specialized from there. Any idea if polyglot supports Substrait?

  7. snth commented on Mar 6, 2026

    @snth
    Member

    My ANSI SQL comment was the wrong approach. I just skimmed over polyglot and I think there is actually a lot that could be done with it. I'll try to research it a bit more in depth.

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