Been using this for a toy project, and enjoying it so far!
Something I haven'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.
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?
To be clear, the query compiler (that turns an EdgeDB query into a SQL query) is written in Python. And AFAIK, compiling the query should be very fast compared to actually executing it!
Learning projects for proof-of-concept can be written in Python, but not a production database. It seems that Rust has been working its way from the corners towards the core. For instance,the edgedb-cli is a rather elaborate rust project.
Hopefully, the adoption of Rust continues through the rest of the project. I love Python but it's not the right tool for the job.
I think this is awesome. This is like higher level and more readable + hopefully more efficient version of SQL.
BTW: In the nested-filters example, I don't understand how actor's `name` is being returned as `actor_name`. Where is `AS actor_name` being specified in EdgeDB's query?
It isn't. The quer returns an array `actors`, each of which has a property `name`. The SQL doesn't produce the same output, it's more like the SQL you'd write to solve the same problem.
Btw you can copy that example into the previous executable example input box and remove the reviews part to execute it.
That was my first reaction too. However, unlike the no-SQL monstrosities (like Mongo), this one seems to sit on top of a proper relational database, plus it seems to follow all the ol' good data modelling logic, just in a modern ish way, so I think it looks promising.
I'm not going to switch all my clients to it next week :) But it is definitely on my radar.
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
I think the parent comment meant the query libraries. The EdgeDB page lists "first-party clients for your favorite languages." They have clients for JS/TS, Go, Python, etc... but no Java/Kotlin yet.
Something I haven'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.