Live data from Hacker News

EdgeDB 2.0

edgedb.com

141–150 of 150 posts

Re: EdgeDB 2.0

#141
post #60

Congratulation on the 2.0 release. EdgeDB looks awesome. However, I will not advocate using it for any of my clients unless there's a clear path to derisking its adoption. Like all new software products/services there's a significant risk of it becoming abandonware. I'd obviously want EdgeDB to succeed but how can one de-risk adopting it? Would it be possible to somehow "transpile" both queries and modeling scripts t…

I'm working on a npm package [1] that "transpile" from a syntax inspired by edgedb into raw sql. The generated sql and be used with original database, without additional running process.

I've implemented select columns, join tables and where statements. Still having more to work on (e.g. order by, group by, aggregate function, and more important, the readme)

[1] https://github.com/beenotung/better-sql

Re: EdgeDB 2.0

#142
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…

> But the demand from the community for this feature has been so far pretty low.

Makes sense since most read queries can (probably) be performed already with EdgeDB.

But my point about executing raw SQL was regarding having an escape hatch for features like listen/notify, etc.

I guess the solution is that for now apps will need a second PG client. Do you anticipate any problems with that approach?

Re: EdgeDB 2.0

#143
post #132

Earlier quoted context omitted.

General client question: Which ones do you intend to officially support? Interested in Elixir client that is now community maintained.

https://www.edgedb.com/roadmap#client-language-bindings According to the roadmap: - Python, Javascript/Typescript, HTTP are done - Go, Rust, Ruby, Java, and .NET are planned Looks like it hasn't been updated now that Rust is out. But seems like those are the languages planned.

We already have a Go driver as well[0] and you can get pretty far by executing queries over HTTP[1] though that's not as capable as a full client. As you said, the roadmap needs some freshening up.

[0] https://github.com/edgedb/edgedb-go

[1] https://www.edgedb.com/docs/clients/http/index#edgeql-over-h...

Re: EdgeDB 2.0

#144
post #82
post #81

Earlier quoted context omitted.

Isn't EdgeDB a python program? I fear python packaging - especially inside a browser or Android device.

It's a mix of Python, C, Rust, Cython, etc. It's fully safe-contained though, the fact that there's some Python inside is an implementation detail, you'll never know that as a user.

but, I would know as an app builder if I was running EdgeDB against a local datastore on a user's device, right?

Re: EdgeDB 2.0

#145
Hey EdgeDB, SQLAlchemy guy here!

EdgeDB is of course beautiful but any thoughts on how the Python client might support pep-484 integration? if all the queries are strings, the Python code has no way to know anything about what datatypes the returned records would have, unless you spell it out explicitly for every query which is very cumbersome. You'd need something that looks more like SQLAlchemy's class definitions corresponding to EdgeDB types for that to be possible (that is, something that looks more like a Python DSL/ORM type of thing).

Re: EdgeDB 2.0

#147
post #98

I actually dig the declarative schema syntax. Is it something separate that one can use in various programming languages, or is it specific to EdgeDB?

It's specific to EdgeDB. And part of what makes it great is a tight integration with our query language - EdgeQL. You can specify aliases, default expressions, access policies with arbitrary EdgeQL expressions in your schema. Fun fact: our schema declaration language is actually a trimmed down DDL syntax of our query language.

Thanks for responding.

I am asking because more and more I see a need for universal type-describing language, one that transcends the programming languages and can be used for various things e.g. specifying DB schemas, code-level invariants, generating network clients to interact with a service, and many others.

It's a passion and I am going around gathering data on such syntaxes and trying to ascertain their viability. Your answer helped.

Re: EdgeDB 2.0

#148
Questions:

SQL schemas are rigid and hard to refactor, does EdgeDB solve this?

I would like to know more about why building a graph db on top of postgres will be better than building a native graph database directly? (With numbers, not "pg is fast")

Re: EdgeDB 2.0

#149
post #6

I want to build local first software backed by EdgeDB. Similar to these tools: - https://replicache.dev - https://github.com/tantaman/conflict-free-sqlite - https://aphrodite.sh I wonder if EdgeDB provides any utilities to make this already perhaps? Or community has to build some kind of CRDT software that builds on top of EdgeDB that will do local syncing? Maybe that's planned to be tackled for 3.0?

Curious if you've taken a look at ChiselStrike (disclaimer: founder here) ChiselStrike translates typescript to sql transparently (https://blog.chiselstrike.com/my-other-database-is-a-compile...) and works well with Replicache (https://blog.chiselstrike.com/offline-data-access-a-dream-co...)
Post reply on HN