Live data from Hacker News

EdgeDB 2.0

edgedb.com

121–130 of 150 posts

Re: EdgeDB 2.0

#121
post #115

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

It's great... Until people start abusing it as an ineffective copy protection mechanism.

Re: EdgeDB 2.0

#122

Earlier quoted context omitted.

Alas, we have to wait until CockroachDB becomes a bit more capable SQL-wise. I gave a more elaborate answer in https://github.com/edgedb/edgedb/discussions/3403 .

> To realize the full potential of ... EdgeQL efficiently, we must squeeze every last bit of functionality out of PostgreSQL's implementation > That said, EdgeDB, the implementation, and EdgeQL, the language and the model, are different, and we encourage research into alternative EdgeQL implementations. We'll be releasing the formal EdgeQL spec and the graph-relational model whitepaper to make this easier. Has the me…

Not yet. Our reference documentation is extremely thorough though, an implementor of an alternative backend should be able to use it.

Re: EdgeDB 2.0

#123
post #107

Earlier quoted context omitted.

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

I think you'll be able to use Django alright, but half of its value prop is their ORM and admin panel. Both of which you don't need with EdgeDB.

Re: EdgeDB 2.0

#124
post #44
post #43

Can you improve the deployment story for wireguard to match the native PostgreSQL experience? Currently deploying EdgeDB requires setting up multiple VPN connections and environmental variables. Ideally it should be one click, zero-config just like Postgres.

Yeah, that will all be simplified when we launch our cloud. Our goal is to make it possible to deploy to cloud with one short cli command. We'll have it soon.

Please also provide the migration guide from existing database provider to your cloud when it launched.

Re: EdgeDB 2.0

#125
Could you use efficiently query a page for all its comments? Like an HN page or Reddit page?

Currently I’m using materialized paths to handle this but it would be awesome if I no longer have to as it’s a bit of a hairball

Re: EdgeDB 2.0

#126

Could you use efficiently query a page for all its comments? Like an HN page or Reddit page? Currently I’m using materialized paths to handle this but it would be awesome if I no longer have to as it’s a bit of a hairball

Efficient transitive closure (aka link recursion) is something we plan to tackle soon (see https://github.com/edgedb/edgedb/discussions/2634 for some discussion on the topic).

Re: EdgeDB 2.0

#127
post #115

Earlier quoted context omitted.

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

It's great... Until people start abusing it as an ineffective copy protection mechanism.

people can already do that with javascript anyway

Re: EdgeDB 2.0

#128
post #2

EdgeDB co-founder and CEO here. Ask me anything. We are streaming EdgeDB 2.0 launch event right now, join here: https://www.youtube.com/watch?v=1jloGHV31Ow

congrats on this milestone.

I’m currently using a graph database (dgraph) mostly so I can easily query complex relationships), and I’m wondering whether EdgeDB has similar performance due to how it stores data?

my understanding of EdgeDb is that it stores everything in a single table, and there’s an underlying graph structure. does this give added performance on complex queries?in other words, does EdgeDB perform complex queries involving multiple relationships better than an equivalent complex Postgres JOIN query? how does the performance compare to the average graph database for queries involving complex relationships? has it been performance tested on complex queries?

Re: EdgeDB 2.0

#129
post #97
post #90

Earlier quoted context omitted.

I asked on Twitter but I'll ask again here :) What's the current approach for triggers, subscriptions, etc? Can you perform raw SQL queries through your client or do apps still need to use a separate PG client for that?

Triggers might make it to 3.0, but we'll have to write an RFC and see if it's doable in the timeframe we have for it and given the other higher priority items on the ToDo list. We contemplated mentioning them in the 2.0 blog post but decided not to over-promise :) Regarding subscriptions -- polling is the current best (and unfortunate) answer. We'll keep researching this area. > Can you perform raw SQL queries throug…

> Not yet. We plan to eventually allow read-only SQL queries to go through EdgeDB for plugging existing analytical tools/BI. But the demand from the community for this feature has been so far pretty low.

It's interesting you say this. This is the reason I passed on EdgeDB. If it was additive to SQL (you can use EdgeDB optionally) that would be great. Im not sure people would ask for it, but given the option everyone would use it.

Re: EdgeDB 2.0

#130
post #2

EdgeDB co-founder and CEO here. Ask me anything. We are streaming EdgeDB 2.0 launch event right now, join here: https://www.youtube.com/watch?v=1jloGHV31Ow

congrats on this milestone. I’m currently using a graph database (dgraph) mostly so I can easily query complex relationships), and I’m wondering whether EdgeDB has similar performance due to how it stores data? my understanding of EdgeDb is that it stores everything in a single table, and there’s an underlying graph structure. does this give added performance on complex queries?in other words, does EdgeDB perform com…

EdgeDB stores data in a fairly normalized table layout, where every object type corresponds to a physical table.

The performance of deep hierarchical queries with EdgeQL will be better than SQL with joins because with joins you'd have an unnecessarily wide denormalized set of rows. EdgeDB instead aggregates data in nested arrays via subqueries. The performance is great.

https://github.com/edgedb/imdbench

Post reply on HN