plprql

Data

postgres extension

SHOW HN2024

267points
139comments
#267of 3,515 in 2024
Top 8%of 2024 by points

How HN took it

MixedNo clear lean

14 positive, 17 neutral or asking, 7 mixed, 11 critical, out of 49 comments about the project. Thread score +0.09.

Idea: 8 for, 8 againstDesign: 4 for, 2 againstExecution: 2 for, 0 againstPerformance: 0 for, 1 against

The thread, comment by comment

Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.

positive neutral or mixed critical about another commenter or something else the maker

What HN said

What people liked

  • PRQL is more readable and convenient than SQL for analytical queries.

    From 2 comments
    • This comes up every time PRQL makes it onto HackerNews and is a fair question: Short answer: DX Slightly longer answer: Developer productivity and experience, especially for EDA…
      snthpy on HN
    • Sorry to be that guy :-) The `introduction.prql` example on the playground gives an idea of the better readability of PRQL vs SQL and your small example an idea of the speed you…
      lkuty on HN
  • Rust/pgrx extensions are a good approach.

    From 1 comment
    • Nice to see extensions like this one developed in Rust/pgrx. Reminds me of https://github.com/tcdi/plrust
      landingunless on HN

Objections

  • Windows is not supported because pgrx lacks Windows support.

    From 1 comment
    • This extension has been developed on top of pgrx and depends on the platforms that pgrx supports. From the pgrx readme: > Windows is not supported. It could be, but will require…
      kaspermarstal on HN
  • The PRQL example is no simpler than plain SQL.

    From 2 comments
    • > How long would it take you to write the SQL for that? I don't want to appear rude, but unless I'm missing something, this is a pretty simple SQL query, of the kind anyone with…
      GordonS on HN
    • I have a moderate amount of SQL experince, but I could not write that query at the top of my head. Maybe you misunderstand what the PRQL query is doing? Here's the SQL it…
      audunw on HN
  • Adds an abstraction layer over SQL with unclear benefit.

    From 2 comments
    • I don't understand the need for libraries that abstract away SQL when you could just write SQL directly and have full access to the power of the language which is quite rich…
      lkuty on HN
    • Eh, `DISTICT ON` is a custom PostgreSQL extension. A standard* method would be: ``` SELECT * FROM tracks QUALIFY row_number() over (partition by album_id order by milliseconds…
      da_chicken on HN

Requests

  • Support for Windows.

    From 1 comment
    • Why is this PRQL extension for Postgres limited to Mac and Linux? What dependencies on Windows are the obstacles, and is there an expected solution in the near-term?
      dataspun on HN
  • Compatibility with Grafana.

    From 1 comment

Questions

  • Is PRQL faster than standard SQL?

    From 1 comment
    • Is PRQL faster than the standard query model?
      mt_ on HN

Alternatives named

  • Ecto

    From 1 comment
    • Very interesting, it looks a lot like the Elixir package Ecto that has a DSL for writing SQL queries. Obviously there are some differences here and I wonder if the compiler can…
      andy_ppp on HN
  • Microsoft Kusto query language

    From 1 comment
    • It looks a lot like Microsoft’s Kusto query language which is a pleasure to use. Piping is better than nesting and from-first is the way to go as it’s necessary for autocomplete.
      brikym on HN
  • Malloy

    From 1 comment
    • There are very interesting improvements to SQL, which are much more ergonomic, extend functionality, and provide higher-level abstractions. Also backward compatible. PRQL and…
      mikpanko on HN
  • jq / pgJQ

    From 1 comment
    • Nice work. A few months back, I experimented with having a DSL like PRQL in Postgres, but back then, I found the language a bit cumbersome; however, it was great as an idea.…
      fforflo on HN

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/39428609)