EdgeDB – A graph-relational database built on top of Postgres

Been using this for a toy project, and enjoying it so far!<p>Something I haven&#x27;t quite figured out is, when using the TypeScript library, how to have more than two filters, ie x == z and y == a and b == c, without some pretty nasty nesting using the .op function.

I love this project. But what they need before I&#x27;d use it in prod is, the equivalent of an EXPLAIN command.<p>It&#x27;s a pretty common problem for a developer to have: &quot;this query looks like it should be fast, but actually it&#x27;s slow. What&#x27;s the DB doing?&quot;<p>I thought I saw somewhere that EXPLAIN was coming in EdgeDB 3.0(?)

Another query language? Why can&#x27;t they just implement Cypher... I still have nightmares from trying to learn ArangoDB&#x27;s AQL.

This is one of the projects that I’m really excited about. The thing that concerns me are it’s performance characteristics with it being written in Python. Vs something like PostgREST which is written in Haskell and blazing fast. Is there more info about performance and scaling of Edge?

How does this compare to graph databases like neo4j? Would anyone recommend using this for working with actual graph data structures?

How does recursion &#x2F; recursive queries work, e.g. tree-like data structures? How are cycles represented and handled? Particularly around performance?

Previous discussions on HN:<p>[1] Show HN: EdgeDB 1.0 (145 comments):<p><a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=30290225" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=30290225</a><p>[2] EdgeDB 2.0 (323 comments):<p><a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=32267287" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=32267287</a>

I think this is awesome. This is like higher level and more readable + hopefully more efficient version of SQL.<p>BTW: In the nested-filters example, I don&#x27;t understand how actor&#x27;s `name` is being returned as `actor_name`. Where is `AS actor_name` being specified in EdgeDB&#x27;s query?

&gt; The post-SQL era has arrived<p>Here we go again.

This is awesome and I really hope it succeeds but using it at my company means I’ll have to answer, “why can’t we just use SQL” a million times from every engineer who is dreading learning a new thing

No Java&#x2F;Kotlin driver.

It&#x27;s not as simple as it shows from basic examples.<p>Complex stuff gets weird.