1st1

21 ms·

211.
by 1st1 5y ago
The key insight here is that we still have schema. We have high-level object types and a first-class notion of a "reference" - we call it "link". Our other extension of the relational model is that every "row"
212.
by 1st1 5y ago
For the full story read another blog post: https://www.edgedb.com/blog/building-a-production-database-i... :)
213.
by 1st1 5y ago
Thank you!
214.
by 1st1 5y ago
If you use a graph database to store application data and you want a strict schema (and potentially improved performance), then YES. If you use a graph database to run graph algorithms on your data, then NO. Although we'll be working o
215.
by 1st1 5y ago
Our topmost priority now is launching a hosted version of the product, all hands on deck. Having a proper (and potentially fully type-safe) query builder for Python is literally the next to-do.
216.
by 1st1 5y ago
Thank you. The feature set is indeed pretty deep. We are going to have a C# client for sure, but I don't have any ETA yet. FWIW you can interact with EdgeDB over HTTP!
217.
by 1st1 5y ago
Thanks! The secret sauce is to pack nested shape queries into array_agg-ed SQL subquery. So we never select unnecessarily wide rows.
218.
by 1st1 5y ago
EdgeDB co-founder Yury here. Ask me anything :) Live launch stream: https://www.youtube.com/watch?v=WRZ3o-NsU_4
219.
by 1st1 5y ago
> One more thing that can make me happy is to see if connection cost to EdgeDB is much lower than PostgreSql It is. Connecting to EdgeDB is cheap and we have no problem handling thousands concurrent connections.
220.
by 1st1 5y ago
Thank you for great feedback! > in edgedb console shell if you hit Enter key it doesn't execute the query, but breaks the line. So there is an extra step to move cursor back to the end of the query before executing it You should be
221.
by 1st1 5y ago
Oh, that's very real with EdgeDB! We used to have a React UI framework for exactly this: ease the pain of generating server and client code for form and data-grid components. You could either describe a form layout in declarative YAML
222.
by 1st1 5y ago
Python allows for high development velocity. Combined with our knowledge of the ecosystem and understanding of the limits to which we can push Python, as well as EdgeDB using Postgres as foundation, it wasn't an unreasonable choice. We
223.
by 1st1 5y ago
Thanks! > 2- The schema you have designed helps a lot on the server-side. If this schema can be extensible (that is, people can make extensions by allowing extra information in the schema that the DBMS ignores, similar to comments) and a
224.
by 1st1 5y ago
We call EdgeDB a graph-relational database. Its type system is essentially a graph of object types, yet out set-based query language and the fundamental data model are still relational.
225.
by 1st1 5y ago
Yeah, that's true - Postgres is the engine. On top of that we have a lot of infra though: our IO server (amongst other things it acts as a server-side connection pool), compilers to compile our query language to SQL behind the scenes a
226.
by 1st1 5y ago
Thanks! > Not the most conventional choice. Yeah... :) To be clear we've already started rewriting parts of core EdgeDB in Rust with the goal to rewrite the IO server in the next year. Some less performance-critical parts of it will
227.
by 1st1 5y ago
Thank you! EdgeDB is fundamentally a relational database -- it has a schema and a powerful query language. It makes sense to store application data in it (just like you would in Postgres or MySQL). It's a general purpose DB. neo4j is
228.
by 1st1 5y ago
Hi there! I'm Yury, the author of the blog post. Ask me anything about contributing to Python, uvloop, or, of course, EdgeDB! Most importantly, EdgeDB 1.0 is launching live in just a couple of weeks. Join our live launch event here: [1
229.
Building a production database in ten years or less(edgedb.com)
94 points by 1st1 5y ago|34 comments
230.
by 1st1 5y ago
Hm, and just recently WhatsApp management mocked Apple, bragged about their encryption, and said how they would never do anything like that. https://twitter.com/wcathcart/status/1423701473624395784?s=2...
231.
by 1st1 5y ago
> I expect EdgeDB's GraphQL implementation just translates to EdgeQL/SQL and can simply optimise that. Yeah, that's what we do. Any GraphQL query can easily be compiled to an EdgeQL (as it's a superset language) query
232.
Only action against corruption can solve the world’s biggest problems(theguardian.com)
46 points by 1st1 5y ago|13 comments
233.
by 1st1 5y ago
Very well put. :) // I work at EdgeDB
234.
by 1st1 5y ago
You guessed everything right: we run an instance to prerender and cache at the build time and at runtime we query when the query has been changed
235.
by 1st1 5y ago
We plan to implement splats soon, e.g.: SELECT User { ...User }
236.
by 1st1 5y ago
Let us know how it goes!
237.
by 1st1 5y ago
Yes, we contributed a few patches and bug reports over the years. We are using vanilla Postgres since it hit 12 and now contains our fixes (or fixes proposed by us).
238.
by 1st1 5y ago
It already has it. In addition to the binary protocol you can shoot GraphQL or EdgeQL queries at it via HTTP.
239.
by 1st1 5y ago
Not yet. Our CLI is written in Rust and we have crates for the protocol and other pieces, but their APIs are not stable yet. It is on our roadmap though.
240.
by 1st1 5y ago
If you decide to go the EdgeQL route first we have some great learning materials, e.g. here's a book about EdgeQL: https://www.edgedb.com/easy-edgedb

More ›