prql
prql copied to clipboard
PRQL
PRQL is a modern language for transforming data — a simple, powerful, pipelined SQL replacement
Currently `from s""` is not allowed. We'd like to make this possible, both for https://github.com/prql/prql/issues/918, and because it's a general & orthogonal language feature. As part of that we can...
I've been adding some integration tests to dbt-prql, and unfortunately it doesn't work with the dialects that use double-quotes. That's because: ```elm from in_process = {{ source('salesforce', 'in_process') }} ```...
TODO: - [ ] basic tests - [ ] tests for function curries and pipelines - [ ] replace join `side:` argument with to `nulls_left:` and `nulls_right:` - [x] figure...
Continuing discussion from Discord: https://discord.com/channels/936728116712316989/1001415848902283284 In short, we have to decide for each operator how it handles null inputs. My guiding principle would be that we should not throw errors...
Currently, querying files in DuckDB doesn't quite work without an alias, because: ```elm from products.csv filter supplierID == 1 ``` compiles to: ```sql SELECT products.csv.* FROM products.csv WHERE supplierID =...
We're starting to write more dialect-specific code in `translator.rs`; e.g. https://github.com/prql/prql/pull/858 What's the best design for this? - Currently we have a mix of methods on `Dialect` structs https://github.com/prql/prql/blob/a1919f5504974878a1f8c763cb43cb5cac4f7d7f/prql-compiler/src/ast/dialect.rs#L90-L97 and...
I get an error when running the example at https://pypi.org/project/prql-python/ # Code ```python import prql_python as prql prql_query = """ from employees join salaries [emp_id] group [emp_id, gender] ( aggregate...
In some cases, PRQL does nicely warn us whenever we're referencing a field name that could have multiple meanings: ``` Ambiguous reference. Could be from either of `option_a`, `option_b` ```...
The PRQL syntax currently usually (with the exception of lists?) treats newlines as terminating characters for statements. (And please do correct me if I'm wrong about this!) For long expressions...
This is still a WIP -- I'm getting a error in semantic which I need to spend some more time on. Any thoughts on the language design? Currently this has...