PRQL 0.2

Congrats for the milestone!! The syntax looks more intuitive than SQL. Great to see viable alternatives to SQL!

This reads a lot like the style of Pandas I teach.[0] This seems to have resolved a problem with SQL, you can't read it in a linear fashion. When we start getting query…

I've seen similar solutions being built internally in multiple companies, none with a syntax as well thought out as this. Amazing work!

I've been contributing to this project on a few little things due to my little knowledge level. But I felt like home with such a good company of people!. I not mature enough to…

SQL doesn't need fixing or improving if you ask me, its well supported and just works.

Hot takes: SQL is great, actually. This thing isn't better.

Why should I use this instead of SQL?

From a mathematical point-of-view are there any transforms/operations (note: not end results, but actual operations) that this can do that SQL can't or vice-versa?

Obligatory dismissive comment: > 0.2 No it ain't (in production). Anyway, this looks great. I LOVE the fact that you've provided a book too. Consider me a fan!

I'm surprised that none of the examples on Github or the website deals with join. I eventually found some in the "book" here: https://prql-lang.org/book/transforms/join.html ```…

Here's one suggestion: SQL tediously requires specifying the equality condition on joins, when 90% of the time you just want to join on the fk defined between the tables. ```…

Wow! This is cool stuff. I was looking through the documentation for conditional logic, control flow, IF(), and the CASE...WHEN...THEN operator. It seems like the ternary…

I see that the JavaScript package is at [1] and it's implemented by compiling the Rust code to WASM. That should eventually make it pretty easy to run it. It has a typescript…

Looks fantastic. There are a lot of rough edges when building a string representing an SQL query in the programming language that you're using. You have to be careful to avoid…

It seems like an obvious next step for Postgres support would be to make PRQL a stored Procedure Language. create function foo() returns bar as language prql $$<prql code here>$$;

I also recommend looking at EdgeQL -- https://www.edgedb.com/showcase/edgeql -- a new query language aimed to eliminate some of the SQL quirks. (I'm a co-founder)

This sounds like LINQ, or SparkSQL. Instead of a full new language, it makes feel better to create libraries in languages that supports embedded DSL easily.

Looks a lot like LINQ

For those interested in database query languages, it is worth knowing about Datalog, the query language behind Datomic, XTDB and Datahike: http://www.learndatalogtoday.org/ E.g.…