Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

EdgeDB 2.0

edgedb.com

Post reply on HN
Print view View original

111–120 of 150 posts

Re: EdgeDB 2.0

#111

Post by Kabootit »

upupandup wrote: post #53
turtlebits wrote: post #49

Been using EdgeDB for ~6 months and it's great. I do wish the documentation was better (more examples please!). I spent more time than should be necessary trying to figure out simple things like NOT NULL, or how to get a backref for a linked table.

im hesitant to bet the horse against something this young. I can see the allure of it but there are just as many equal me-too ORMs on top of postgres. The idea of graph-relational is interesting but I'm not sure the pain points it describes (having to use JOIN) is enough to get me to use EdgeDB since it's not really an issue for most use cases unless you are doing very complex queries across dozens of tables. There w…

There is prior art for the "object relational" databases. Used WakandaDB (from the 4D creators) ~10+ years ago fairly heavily and in most ways it was way ahead of its time.

The UI editor was fantastic: https://raw.githubusercontent.com/datamosaic/data-sutra-waka...

The query language was imperative in the "fluent" style:

var record = ds.Group.query("name = :1",group).first();

Really psyched about what EdgeDB is doing moving this space forward. The declarative composable query language is a paradigm shift imo — not just a better ORM.

Re: EdgeDB 2.0

#112

Post by tadfisher »

qwertox wrote: post #56
fnord123 wrote: post #40

Earlier quoted context omitted.

Couchbase-lite seems to do what you're asking. It's backed onto sqlite. It's more sync based than crdt based afaict.

Adding ObjectBox to the list. https://objectbox.io/

Unfortunately ObjectBox has a proprietary core, which is unfortunate as I'd love to modify it for experimental uses.

Re: EdgeDB 2.0

#113

Post by sedatk »

RedCrowbar wrote: post #77
sedatk wrote: post #71

Earlier quoted context omitted.

Why's NOT NULL a problem? ("required property" syntax is already in quickstart examples)

I think the OP meant `NOT NULL` as in nullness check in queries. EdgeQL uses `exists ` to check for existence of data. We have examples in the cheatsheet and elsewhere but it's probably hard to find if you're looking for "NOT NULL" specifically. We'll see about a way to improve the discoverability of this.

I see, that makes sense, thanks.

Re: EdgeDB 2.0

#114

Post by sedatk »

laszlokorte wrote: post #99

I just took a look at the quickstart guide. The way the code snippets are implemented is gorgeous. They are syntax highlighted, are formatted/indented exactly as they would be in the terminal, line breaks are indented correctly but css is used to make them easily copy/pastable without including any line numbers/indentation characters. Such a delight. Such focus on details. Makes me really confident in the rest of the…

I agree. There was a small glitch where the field year was defined as release_year at the beginning. I wanted to submit a PR but it was already fixed on github version, just not published yet.

Re: EdgeDB 2.0

#115

Post by jeshin »

laszlokorte wrote: post #99

I just took a look at the quickstart guide. The way the code snippets are implemented is gorgeous. They are syntax highlighted, are formatted/indented exactly as they would be in the terminal, line breaks are indented correctly but css is used to make them easily copy/pastable without including any line numbers/indentation characters. Such a delight. Such focus on details. Makes me really confident in the rest of the…

TIL about user-select:none;

That's useful, I hate copying code snippets alongside line numbers and other weirdness

Re: EdgeDB 2.0

#116

Post by 1st1 »

jeshin wrote: post #115
laszlokorte wrote: post #99

I just took a look at the quickstart guide. The way the code snippets are implemented is gorgeous. They are syntax highlighted, are formatted/indented exactly as they would be in the terminal, line breaks are indented correctly but css is used to make them easily copy/pastable without including any line numbers/indentation characters. Such a delight. Such focus on details. Makes me really confident in the rest of the…

TIL about user-select:none; That's useful, I hate copying code snippets alongside line numbers and other weirdness

We use it throughout our UI in all interactive elements. It's super annoying when, say, a button or a navigation element gets accidentally selected for no reason.

Re: EdgeDB 2.0

#117

Post by inferiorhuman »

laszlokorte wrote: post #99

I just took a look at the quickstart guide. The way the code snippets are implemented is gorgeous. They are syntax highlighted, are formatted/indented exactly as they would be in the terminal, line breaks are indented correctly but css is used to make them easily copy/pastable without including any line numbers/indentation characters. Such a delight. Such focus on details. Makes me really confident in the rest of the…

I had no idea what EdgeDB is/was so I took a look at the site. The first thing that stood out was a typo (that's instead of that). It's since been fixed, but I had to chuckle at attention to detail.

Re: EdgeDB 2.0

#118

Post by canadiantim »

1st1 wrote: post #107
abdellah123 wrote: post #106

Congrats. EdgeDB is really a game changer. One thing I'm excited about is a framework that uses EdgeDB instead of ORM+SQL. This would make the framework itself leaner and lead to writing less code since the db can do so much more!

Thanks! Depends on what kind of frameworks you like. EdgeDB+Next.js or EdgeDB+Flask are very pleasant to use already. But there's no heavyweight one like Django or RoR just yet.

Would you foresee any difficulties using EdgeDB with Django?

I know there would be no need to use Django's ORM and migrations if using EdgeDB - but then again I might use EdgeDB and SQLite (for FTS in the near term and mobile/offline in the long term), so maybe Django migrations still helpful there

Re: EdgeDB 2.0

#119

Post by 1st1 »

cpursley wrote: post #96
1st1 wrote: post #57

Earlier quoted context omitted.

Yes, we're building that capability. With 2.0 we made our protocol stateless and can tunnel it through HTTP now, allowing access to full APIs of our clients. (Although EdgeDB also exposes a REST endpoint that you can access with any HTTP client from any language). We'll be working on tightening and adding the necessary security mechanisms to allow exposing the DB directly to web in 3.0 and onward.

This would be great. I'm a big fan of Hasura and not having to write crud apis. But would prefer having more or less the same query language on all clients.

Yeah, that's the dream. But there are lots of tiny details to figure out to make it really usable in prod and not gimmicky. Hasura is a great product indeed.

Re: EdgeDB 2.0

#120

Post by 1st1 »

Kabootit wrote: post #111
upupandup wrote: post #53

Earlier quoted context omitted.

im hesitant to bet the horse against something this young. I can see the allure of it but there are just as many equal me-too ORMs on top of postgres. The idea of graph-relational is interesting but I'm not sure the pain points it describes (having to use JOIN) is enough to get me to use EdgeDB since it's not really an issue for most use cases unless you are doing very complex queries across dozens of tables. There w…

There is prior art for the "object relational" databases. Used WakandaDB (from the 4D creators) ~10+ years ago fairly heavily and in most ways it was way ahead of its time. The UI editor was fantastic: https://raw.githubusercontent.com/datamosaic/data-sutra-waka... The query language was imperative in the "fluent" style: var record = ds.Group.query("name = :1",group).first(); Really psyched about what EdgeDB is doing…

> The declarative composable query language is a paradigm shift imo — not just a better ORM.

This!

Post reply on HN