EdgeDB co-founder Yury here. Ask me anything :) Live launch stream: https://www.youtube.com/watch?v=WRZ3o-NsU_4
Dumb question, how do you exit the shell? I feel like I've scoured the docs and can't find it.
Show HN: EdgeDB 1.0
191–200 of 332 posts
Re: Show HN: EdgeDB 1.0
#192This query language looks really nice! I wish GraphQL were more like this and considered built-in features like where clauses and cursors, instead of having to add those over the top with loose conventions.
GraphQL is great for what it was designed for. It just was never designed to be a querying language with analytical capabilities, like EdgeQL.
Re: Show HN: EdgeDB 1.0
#193Earlier quoted context omitted.
Thank you! Please do and feel free to connect with us to discuss your experience :)
if easy to answer: can this be used with eg AWS RDS? or is there something that couples the postgres engine tightly enough that's not doable?
Yes, it can be used with rds or aurora, we have guides in the docs.
Re: Show HN: EdgeDB 1.0
#194Earlier quoted context omitted.
A lot to unpack here. 1. If other clouds want to offer a hosted EdgeDB offering, they can do so. We'll have a tight integration with the `edgedb` CLI and we're confident we can beat them on the developer experience which is our #1 priority. 2. We'll likely use GitHub for auth though this isn't set in stone yet. We're still planning out the workflows surrounding EdgeDB Cloud. 3. As for the explosion of cloud silos—tha…
Fair, thanks for the answers! Honestly hopes it works out for you, but I am very cautious about these things. Elasticsearch, Mongo, Timescale all ended up changing license at some point. Yeah thats ok for startups I guess. Yeah sad state of affair really, though fully solvable by tech IMO if we had some protocol for integrating services in clouds. In any case, please don't underestimate the terraform integration. I r…
Thanks! Point taken re: Terraform, we'll give that some thought.
Re: Show HN: EdgeDB 1.0
#195Earlier quoted context omitted.
So it's basically an ORM over Postgres (and only Postgres)?
We're working on a more comprehensive explanation of why EdgeDB isn't an ORM. Does EdgeDB do "object-relational mapping" under the hood — absolutely. The reason we try to distance ourselves from the category of ORMs is that the term "ORM" comes with a big bag of preconceptions that don't apply here. EdgeDB has: - Full schema model with indexing, constraints, defaults, computed properties, stored procedures - A query…
Re "just an ORM", it seems like the word "mapper" is the hint that it isn't, since there's no "mapping" from the object-oriented view to the big-pile-of-scalars in a traditional relational db.
Re: Show HN: EdgeDB 1.0
#196Re: Show HN: EdgeDB 1.0
#197I’ll add to the positivity: this is the first time I’ve ever found a “we can do better than SQL” compelling. It’s easy to understand what it’s doing with a variety of known quantities. It solves a difficult problem elegantly. It has 100% overlap with the goals I want it to have. It’s designed to be usable with minimal fuss. It does really a good job of portraying itself as magic (it will be awesome to use) without portraying itself as magic (it explains itself in terms of already knowable tools and how it leverages their strength).
I do have a couple minor quibbles:
- Serializable transactions are expensive, and that deserves to be an explicit caveat. Not everyone knows this, and it’s an important thing to put up front.
- Some of the language in this post are in CAP theorem territory but neglect to directly address that. I’d like to see how client usage compares with direct Postgres usage (idiomatic for each insofar as such a beast exists) in a Call Me Maybe. I know that’s a lot to ask in a 1.0 announcement four years in the making, but I hope it’s a priority to get this in front of Aphyr.
Edit: oh and I definitely look forward to this being further distinguished from an ORM, because even though I can see the blue and black dress my mind keeps switching it back to gold and white.
Re: Show HN: EdgeDB 1.0
#198Earlier quoted context omitted.
So as I read TheSpiciestDev's comment, he's complaining that making his query in PostgreSQL is slow. It looks like EdgeDB is a frontend to PostgreSQL; how will it help with TheSpiciestDev's problem?
The problem sounds like something that could be solved with a GIST index. EdgeDB doesn't yet have a way to specify the index type, though, mostly because we aren't sure what would be the best way to do it without things becoming too Postgres-specific in schemas.
What do you mean by "too Postgres-specific"? Will you be supporting other DBs behind the EdgeDB interface in the future?
Re: Show HN: EdgeDB 1.0
#199EdgeDB co-founder Yury here. Ask me anything :) Live launch stream: https://www.youtube.com/watch?v=WRZ3o-NsU_4
I have a few questions I can't find after skimming the documentation..
Can someone use Postgres extensions with EdgeDB, like TimescaleDB, PostGIS, Zombodb and Postgres_fdw?
How are sum types (called enums in Rust) modelled in EdgeDB? (like Rust's Result). Do I need to define it with inheritance, where each variant inherits from it? What about adding specific syntax for sum types?
edit: also, I see there's a WIP custom #[derive] for Rust in https://github.com/edgedb/edgedb-rust - can it store Rust types on EdgeDB? Something like http://diesel.rs/ or even https://lib.rs/crates/turbosql
Re: Show HN: EdgeDB 1.0
#200Earlier quoted context omitted.
How exactly is EdgeDB run? Is it a separate process from Postgres, or some kind of plugin? Can I run it over an existing Postgres instance? If I build a DB Schema in EdgeDB, can I interact with the underlying Postgres instance using regular SQL?
It runs as a separate (stateless) process between the client and the PostgreSQL server. There was a talk about the details of the architecture on the live stream today: https://youtu.be/WRZ3o-NsU_4?t=5294
This sounds very similar to Hasura, which compiles graphQL down to SQL. Have you considered adding the subscription feature like they have?