4 ms·
PRQL as a DuckDB Extension
- kthejoker2 3y agoDisclaimer: I work at Databricks ... so hopefully my subsequent opinion Is worth even more. PRQL and DuckDB are amazing. I've been building a Power BI clone - think low code ETL, semantic layer, dashboards + chatbot - on top of Databricks SQL with PRQL as transformation engine and DuckDB as caching / aggregation layer. (Also huge shoutout to Toby and sqlglot.) So easy to generate things programmatically, PRQL is the perfect map to low code GUIs, Arrow in and out, easy to scale ... Big fan. Every analytics engineer should try them.
- frakt0x90 3y agoI love the idea of PRQL and having a DuckDB extension will make it a lot easier to play with since I'm already using that for my hobby data science projects.
- cced 3y agoCan you share your use of this? I’m interesting in using duckdb and wanted a boost from people with more experience. Currently playing with postgress and dbt.
- datadrivenangel 3y agoYou can replace local postgres with DuckDB and it should be even faster for data analysis.
- vgt 3y agoAnd if you want a severless hosted DuckDB with managed storage, sharing, UI, and ecosystem support, check out MotherDuck[0]! (head of produck at MotherDuck) [0]https://motherduck.com/ https://motherduck.com/
- datadrivenangel 3y agoDo y'all have a reference architecture or templates for local development with CICD pipelines? My last data engineering team struggled to get something like that working with BigQuery, so I'm super excited about the possibility of better data warehouse developer tooling.
- teworks 3y agoI replaced a ton of pandas code with an embedded DuckDB for internal data application and got a massive performance boost and (arguably) cleaner code.
- jeroen79 3y agoSQL is good enough and well established, i see no need for another sql wrapper with a different syntax.
- datadrivenangel 3y agoThere are benefits to improving SQL when you have to maintain hundreds of SQL files for a pipeline.
- setr 3y agoIn the world of application languages, we accept that many languages can exist and compete, and serve various needs and improvements. And we curse the alternative, like that the browser forces us into a single language — JS. In the world of RDBMS languages, we say there is SQL, and only SQL, and none other need ever exist. Ignoring that the SQL standard defines more of an aesthetic of the language than anything actually useful, so you’re only ever dealing with incompatible dialects anyways — there is no one SQL language in practice. Somehow the only way to consider any possible alternative is to drop the relational model altogether, throwing the baby out with the bathwater. I feel like DBA’s have managed to get themselves stuck in the 80’s in terms of tooling; the glory of Codd squirreled away in this great fear of changing anything at all. COBOL is derided by all, and SQL praised unquestionably — I don’t know where it all went wrong
- nerdponx 3y agoI think the concern is more that database engines themselves have a wide range of supported features and functionality, and the variations in SQL mostly reflect the variations in the supported feature set. Developers have also found themselves burned for decades by trying to interact with databases in languages that aren't SQL, including and especially various DSLs and ORM frameworks. The skepticism level is high because the track record for SQL alternatives/replacements isn't good. Maybe PRQL is the one that finally succeeds, but the lack of success until this point is not for lack of trying or imagination.
- setr 3y ago
- datadrivenangel 3y agoThe post-modern data stack is going to be PRQL + DuckDB + Prefect, and it's going to be much smaller and cheaper for most analytics.
- cced 3y agoThoughts on dbt?
- nerdponx 3y agoGreat idea, kind of a chaotic mess in practice. Better than nothing by far, but the industry I think will be eager to receive an improved alternative. The problem with any tool like Dbt that abstracts over differences in databases is that a huge amount of work goes into building "adapters" to support the various details and quirks of each supported database. That ends up being a substantial technological moat which inhibits the growth of competitor systems. Another option is to do what Datasette did and focus on supporting one specific database, gradually expanding to a second database after years of demand for it.
- esafak 3y agoAre you sure prefect is better than flyte? How so? https://neptune.ai/blog/best-workflow-and-pipeline-orchestration-tools https://neptune.ai/blog/best-workflow-and-pipeline-orchestra...
- bonchicbongenre 3y agoI'm with you at least 2/3 of the way. My preferred stack is PRQL + DuckDB + Dagster. I evaluated the space for work at my current company (was originally only DE, handling ingests from ~300 sources across various systems, on order of ~1k downstream tables in dbt + hundreds of dashboards + a handful of business-critical data+app features; now leading a small team). I came away ranking dagster first, prefect second, everything else not close. IMO dagster wins fundamentally for data engineers bc it picks the right core abstraction (software defined assets) and builds everything else around that. Prefect for me is best for general non-data-specfic orchestration as a nearly transparent layer around existing scripts. Ofc to each their own based on their usecase.
- oulipo 3y agoNice! Perhaps you could distribute a NPM package with the WASM extension too? Otherwise the alternative is to use the WASM PRQL compiler, and use that in the browser to generate queries for ducksb-wasm
- amcaskill 3y agoI'm quite excited about this, and would also love to have it distributed as an NPM package. I work on an OSS web framework for reporting/ decision support applications (https://github.com/evidence-dev/evidence https://github.com/evidence-dev/evidence), and we use WASM duckDB as our query engine. Several folks have asked for PRQL support, and this looks like it could be a pretty seamless way to add it.
- oulipo 3y agoI added it using prql-js
- carlopi 3y agoHere it is: https://carlopi.github.io/duckdb-wasm-unsigned////#queries=v0,LOAD-'https%3A%2F%2Fcarlopi.github.io%2Fduckdb%20wasm%20unsigned%2Fthird_party_extensions%2Fpsql.duckdb_extension.wasm'~,from-'https%3A%2F%2Fraw.githubusercontent.com%2Fywelsch%2Fduckdb%20psql%2Fmain%2Fexample%2Finvoices.csv'-%7C-order-by-total-DESC-%7C-limit-10~ https://carlopi.github.io/duckdb-wasm-unsigned////#queries=v... That is, the duckdb-wasm web shell with loaded PSQL extension
- qwertox 3y ago"PRQL is a modern language for transforming data — a simple, powerful, pipelined SQL replacement" [0] [0] https://prql-lang.org/ https://prql-lang.org/
- deleted 3y ago[deleted]
- snthpy 3y ago"Querying DuckDB with PRQL" by Learn Data with Mark (6 min) https://youtu.be/Rdohw424DA4?si=jWydM-LMo2c3ulrh https://youtu.be/Rdohw424DA4?si=jWydM-LMo2c3ulrh PRQL: A Modern Language for Data Transformation (11 min) https://youtu.be/t4-f9vjq2lc?si=Qx3k5oAq5A9THU0G https://youtu.be/t4-f9vjq2lc?si=Qx3k5oAq5A9THU0G
- tacone 3y agoThis is probably stupid but... would scrapscript[1] be a good base for a DSL aimed at replacing SQL? [1]: https://scrapscript.org/ https://scrapscript.org/ edit: added link
- surprisetalk 3y agoScrapscript author here. I'm a huge fan of PRQL and indeed hope to implement a DSL called "scrounge" later this year. The DSL will be nice to have for codegen and type-safety interop inside of scrapscript, but there's no way it would feel as nice as using PRQL directly.
- hintymad 3y agoMaybe, but at least it is not immediately clear to me why scrapscript is better than SQL. The homepage of scrascript says: > Scrapscript is best understood through a few perspectives: > “it’s JSON with types and functions and hashed references” > “it’s tiny Haskell with extreme syntactic consistency” > “it’s a language with a weird IPFS thing” It later says: "Scrapscript solves the software sharability problem." None of the statements addresses the commonly recognized shortcomings of SQLs. In contrast, PRQL's value proposition is clear: it improves the readability and composability of SQL by offering a linear order of transformation through a pipelined structure. In addition, it is based on relational algebra so database professionals can still apply the theoretical framework that they understand and trust to master the language.
- tacone 3y agoHello, thank you for your answer. There's apparently more in scrapscript than what's written on its homepage. I didn't really meant to compare it to PRQL, but at the same time it probably offers some of the propositions of PRQL: extreme composability, functional programming (so: pipelines) and some more.
- didip 3y agoCan someone tell me why PRQL is better? I went here: https://github.com/PRQL/prql https://github.com/PRQL/prql It looks nice, but what's the strengths compared to SQL?
- klysm 3y agoit sounds minor, but having `from` before `select` means you can get autocomplete
- henrydark 3y agoI get the sentiment, but personally I can easily imagine myself writing an autocompleter that would work fine with select before from. (I don't write much sql so I don't) Just to clarify, my point is that when we do write sql most of us start by writing the from part, and even if we didn't I can just offer all columns from all tables I know about with some heuristic for their order when autocompleting in the select part.
- laerus 3y agoWell, you can always type "select from some_table" and then move the cursor back after select and have auto completion. For example Jetbrains DataGrip supports this.
- klysm 3y agoYeah that’s what I do it’s just annoying though
- snthpy 3y agoHave a look at the online playground: https://prql-lang.org/playground/ https://prql-lang.org/playground/ It starts you off with a very well documented example. Try commenting out one of the lines and watch how the SQL on the RHS changes. Each line is a separate transformation and follows a logical flow from top to bottom. IMHO it combines the best of SQL and pipelined DSLs like dplyr, LINQ, Kusto, to name just a few. An advantage over things like Pandas is that it still generates SQL so you can take your compute to where your data is (Cloud DWH) and benefit from query optimisation whereas Pandas has to download all your data first and then follows an eager execution model which doesn't benefit from query optimisation. Polars fixes a lot of data but still has the data transfer probleam and it is not universal whereas PRQL can compile to different dialects of SQL like DuckDB, Postgres, BigQuery, MS SQL Server, ... For a more in-depth overview, watch this: PRQL: A Modern Language for Data Transformation (11 min) https://youtu.be/t4-f9vjq2lc?si=Qx3k5oAq5A9THU0G https://youtu.be/t4-f9vjq2lc?si=Qx3k5oAq5A9THU0G Disclaimer: I'm a PRQL contributor and the presenter of that talk.
- bvrmn 3y agoIt's not very good from prql devs to use artificially bloated (line wise) examples to show SQL is bad. from employees select {id, first_name, age} sort age take 10 vs SELECT id, first_name, age FROM employees ORDER BY age LIMIT 10 Huh? For simple queries SQL is simple. You can't beat it on this field.
- aerzen 3y agoYeah, we use an SQL formatter that is a bit too verbose for most tastes. But I do agree, PRQL is not really needed for simple queries - it starts to shine only when you have 5+ transforms (clauses).
- bdcravens 3y agoI'd love to see good examples of joining across several tables and applying aggregates. These are the types of queries that are a bit tedious to write but where SQL really provides value vs other ways of storing and extracting data.
- timClicks 3y agoThis style of formatting makes more sense when queries become larger. It's also quite good when you want to have readable diffs to review when queries change.
- bvrmn 3y agoSame reasoning then should be applied for PRQL. My issue is unfair depiction of PRQL as "simple" and "concise". BTW most modern differs show changed parts of line which really helps not to bother with diff-friendly formatting.
- up2isomorphism 3y agoWhat’s the advantage to learn a new query language when most of the statements can be done in SQL?
- dang 3y agoRelated: PRQL: Pipelined Relational Query Language - https://news.ycombinator.com/item?id=36866861 https://news.ycombinator.com/item?id=36866861 - July 2023 (209 comments) PRQL: a simple, powerful, pipelined SQL replacement - https://news.ycombinator.com/item?id=34181319 https://news.ycombinator.com/item?id=34181319 - Dec 2022 (215 comments) Show HN: PRQL 0.2 – a better SQL - https://news.ycombinator.com/item?id=31897430 https://news.ycombinator.com/item?id=31897430 - June 2022 (159 comments) PRQL – A proposal for a better SQL - https://news.ycombinator.com/item?id=30060784 https://news.ycombinator.com/item?id=30060784 - Jan 2022 (292 comments)