4 ms·

Elsewhere in the "SQL replacement" space, I'd like to recommend EdgeDB [0]... * The query language is less like COBOL, more like modern languages * Instead of

Elsewhere in the "SQL replacement" space, I'd like to recommend EdgeDB [0]... * The query language is less like COBOL, more like modern languages * Instead of returning rows, queries return objects linked to other objects through properties * Supports both relational and graph queries * ...but it's Postgres under the hood! And it's open-source -- they're planning to make their money through a cloud-hosted solution. [0]: https://www.edgedb.com/ https://www.edgedb.com/

maximilianroos 4y ago
(PRQL core-dev here) Very much agree! We're very friendly with the folks at EdgeDB, have lots of overlap of contributors. They're part of the inspiration behind PRQL [1]. To focus on the differences for a moment: * PRQL is focused on analytical queries, whereas the genesis of EdgeDB was on transactional queries (though I know Yury & the team are building out more analytical capabilities) * PRQL works with any existing database — you can query any tables you have today — and using PRQL doesn't preclude you or your colleagues from using SQL. In exchange for that openness & simplicity, we give up some functionality — we don't yet know the types of all your columns, for example. TBC, EdgeDB has improved on this dimension since their initial product — it's been able to run on a vanilla Postgres instance for a while now, no extensions needed. [1]: https://prql-lang.org/faq/ https://prql-lang.org/faq/
- agumonkey 4y ago
  both projects are very cool, thanks