• BitSound@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    I’ve been following this closely. Out of all the SQL replacements I’ve seen, I think this has the best chance at succeeding, since it transpiles easily to SQL and it’s not tied to any particular DB or tool.

  • deejay4am@lemmy.world
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    1 year ago

    For HackerNews enthusiasts

    • The PRQL compiler is written in Rust
    • We talk about “orthogonal language features” a lot

    LOL spot on tho

  • captainteebs@lemmy.ml
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    1 year ago

    Love this. I haven’t written any R code in years, but I do miss the simple and intuitive syntax of dplyr and the rest of the tidyverse. PRQL looks like it is built on the same philosophy. Can’t wait for it to get fully integrated into dbt.

  • Rough_N_Ready@lemmy.world
    link
    fedilink
    arrow-up
    1
    arrow-down
    11
    ·
    1 year ago

    This looks cool, but I wish it were easier to use. I see you can create files and then have prql’s vscode extension create sql files out of them, but I don’t always have a separate file per query in my app development projects. It would be nice if they could convert snippets - maybe code comments containing prql - that it converts into sql strings.

    • verstra@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      That’s because the tooling is not there quite yet. For what you describe, that would have to be implemented by the compiler bindings for your language. And it’s not that hard - basically one function. But yeah, not there yet.