You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
tobilg/polyglot can be used to support SQL dialects? #5700
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.
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?
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.
Activity
max-sixty commentedon Mar 2, 2026
interesting!!
do you know how feasible packaging would be?
eitsupi commentedon Mar 3, 2026
I haven't seen anything about the contents yet.
snth commentedon Mar 6, 2026
This is cool. I was aware of sqlglot, but there the issue was that it was Python.
snth commentedon Mar 6, 2026
@eitsupi so you're suggesting that prql-compiler produces ANSI SQL and then polyglot could specialise to the target dialect?
eitsupi commentedon Mar 6, 2026
In fact, I'm not sure how much it will be usable.
For example, something like DuckDB's
excludecan be translated directly from PRQL, but I expect that it will become unsupportable once it goes through ANSI SQL.snth commentedon Mar 6, 2026
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?
snth commentedon Mar 6, 2026
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.