Live data from Hacker News

Show HN: EdgeDB 1.0

edgedb.com

141–150 of 332 posts

Re: Show HN: EdgeDB 1.0

#141
post #124

This is so exciting. We can definitely do better than SQL in 2022 and EdgeDB is a step in the right direction. Been using Prisma[0] in production in the past year and a half (which takes the same approach as EdgeDB but currently works for TypeScript and Golang) and I'm so happy. [0]: https://www.prisma.io/

Prisma + Typescript is such a productivity boon, auto completing all query options and database fields. And the results fully typed.

Re: Show HN: EdgeDB 1.0

#142
post #138
post #130

Earlier quoted context omitted.

Is it though? Simple IN with an ORDER BY on the same match will return the correct ranking. More info on ranking here https://www.postgresql.org/docs/current/textsearch-controls....

Am I right in reading this as the parent comment envisioning a “post” table and a “tag” table, and you’re suggest the “post” table just have a “tag” column?

I see just one table

> 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.

My point is, I don’t see SQL query as expensive for this kind of use case. There are easy and native ways to do it.

In case you would like a top notch performance, Redis might be a way to do it. Even a reverse-index would achieve great performance.

Re: Show HN: EdgeDB 1.0

#143
post #124

This is so exciting. We can definitely do better than SQL in 2022 and EdgeDB is a step in the right direction. Been using Prisma[0] in production in the past year and a half (which takes the same approach as EdgeDB but currently works for TypeScript and Golang) and I'm so happy. [0]: https://www.prisma.io/

Prisma did a lot of things right, and we have a ton of respect for the team over there! At the end of the day, building a good, idiomatic API for doing CRUD operations is a hard problem. But building an entirely new query language that fundamentally solves some underlying design flaws and usability issues with SQL is a whole other level of hard.

With EdgeQL, we conclusively solved a lot of these fundamental issues. Now, we're able to use EdgeQL as the foundation of our query builders, which is a huge advantage. We built the first version of the TypeScript QB in ~4 months) and it immediately leapfrogs all the major ORMs in power & expressiveness. But that's only possible because the hard work of designing EdgeQL was already done.

We'll be working on communicating how our query builder works and how it compares to ORMs in some of upcoming posts, stay tuned.

Re: Show HN: EdgeDB 1.0

#144

It's a good sales pitch, but it's not immediately clear what the terms are. I see that there is a company behind this, that there's also a Github repo, and it appears you can install something without paying. But is it entirely open source? If not, what are they selling? What kind of business is this?

We will run and support EdgeDB for you. Here's an expanded answer: https://github.com/edgedb/edgedb/discussions/3377

Re: Show HN: EdgeDB 1.0

#147

It's a good sales pitch, but it's not immediately clear what the terms are. I see that there is a company behind this, that there's also a Github repo, and it appears you can install something without paying. But is it entirely open source? If not, what are they selling? What kind of business is this?

Everything is fully OSS: the database, our client libraries, our CLI. There's a company behind it (I'm an employee) which will make money with a cloud hosting platform, similar to Mongo. We're calling that EdgeDB Cloud and it's still under development. Though you can self-host too on any major cloud. [0]

[0] https://www.edgedb.com/docs/guides/deployment/index

Re: Show HN: EdgeDB 1.0

#148
Nice. This seems so pragmatic - making something to make developers lives easier rather than doing something clever. I could see myself using this in personal projects. (My day job is heavily MS so wont be using it there)

Re: Show HN: EdgeDB 1.0

#149

Earlier quoted context omitted.

EdgeDB is already postgres specific though.

EdgeDB currently is. Graph-relational and EdgeQL are not.

Until another db is graph-relational and can be queried via edgeql those are just as postgres-specific as arrays though, right?
Post reply on HN