Earlier quoted context omitted.
Because that only gives you actor names, not records, and also because arrays aren't a universal SQL feature.
EdgeDB is already postgres specific though.
Show HN: EdgeDB 1.0
121–130 of 332 posts
Re: Show HN: EdgeDB 1.0
#122Can someone from EdgeDB explain why the SQL isn't as simple as what I have below? What am I missing? Why is that cross join lateral necessary: SELECT title, ARRAY_SLICE(ARRAY_AGG(movie_actors.name WITHIN GROUP (order by movie_actors.credits_order asc)),0,5) avg(movie_reviews.score) FROM movie JOIN movie_actors on (movie.id = movie_actors.movie_id) JOIN person on (movie_Actors.person_id = person.id) JOIN movie_reviews…
Re: Show HN: EdgeDB 1.0
#123On https://www.edgedb.com/tutorial/basic-queries/objects , if I change "SELECT User.name;" to "SELECT User.Name;" the page crashes with, "Application error: a client-side exception has occurred." It crashes on Chrome and Edge.
We'll take a look, should be a quick fix.
Re: Show HN: EdgeDB 1.0
#124Re: Show HN: EdgeDB 1.0
#125My example/requirement: I have a user wanting to find best-matching blog posts. Every post is tagged with a given category. There could be 100+ categories in the blog system and a blog post could be tagged with any number of these system categories. A user wants to see all posts tagged with "angular", "nestjs", "cypress" and "nx". The resulting list should return and be sorted by the best matches, to those of least relevance. So, posts that include all four tags should be up top and as the user browses down the results, there are posts with less matching tags.
What I've seen with SQL looks expensive, especially if you search with more and more tags. I may just not know what to search for though, re. SQL. Is there a query against a graph database that could accomplish this?
Re: Show HN: EdgeDB 1.0
#126Congrats - this looks really interesting, and this is coming from a person who generally ignores new shiny database news. Def will be checking this out!
Thank you! Please do and feel free to connect with us to discuss your experience :)
Re: Show HN: EdgeDB 1.0
#127Earlier quoted context omitted.
I'm not too familiar with the CoreData API, but from a quick googling it seems like this is some sort of an ORM on top of SQLite. We position EdgeDB as a database server, not a library, partly because you can interact with it from different programming languages. But we design our client library with focus on API composability, check out our edgedb-js library for example: https://www.edgedb.com/docs/clients/01_js/ind…
Right, but conceptually the way you interact with it is the same. I'm not trying to belittle what you've done. I'm in fact very excited about it. And EdgeDB is very needed because it's just an Apple library currently. Conceptually, my impression is that EdgeDb is relational tables (highly-typed) queried, combined, and modeled as nodes in a graph/tree. Is that conceptually correct? I don't, but I would like to if I co…
Re: Show HN: EdgeDB 1.0
#128I feel like a graph database is a solution to an issue I've faced (and, continue to face) and it may just be because that I haven't spun one up and tried or that the documentation/examples don't stick out. But could someone confirm my feeling? If my feeling is correct, I'd enjoy verifying it with EdgeDB or the like. My example/requirement: I have a user wanting to find best-matching blog posts. Every post is tagged w…
I just happen to have a very similar requirement to yours and was also wondering.
Re: Show HN: EdgeDB 1.0
#129Earlier quoted context omitted.
Sounds like this is not dissimilar from the GraphQL-to-SQL compiler in Hasura, which also brings out surprising performance for wildly nested frontend queries.
Yeah, indeed, Hasura uses json_agg, which is similar but returns you a JSON string. We use array_agg, so we often avoid data serialization altogether. Our binary protocol just lets the data messages pass through with the original binary encoding. And because we fully control the schema, we can make all sorts of interesting optimizations, like implementing high-perf data codecs on the client side to unpack data fast.
Hasura has the frontend safe API and strong authz going for it. Is that something you might also do, or are you focused on serving the backend? End-user row and column level authz gives me a lot of peace of mind when writing bigger queries.
Re: Show HN: EdgeDB 1.0
#130I feel like a graph database is a solution to an issue I've faced (and, continue to face) and it may just be because that I haven't spun one up and tried or that the documentation/examples don't stick out. But could someone confirm my feeling? If my feeling is correct, I'd enjoy verifying it with EdgeDB or the like. My example/requirement: I have a user wanting to find best-matching blog posts. Every post is tagged w…