1st1

27 ms·

301.
by 1st1 8y ago
The benchmark results are right in the blog post.
302.
by 1st1 8y ago
> So how is a missing value in a column represented? Explained in this thread: https://news.ycombinator.com/item?id=19641060 > > Functions in SQL can return NULL to signal an error condition. > That's plain
303.
by 1st1 8y ago
We maintain the number of modifications to the minimum, and we don't touch critical paths (there's simply no need for that).
304.
by 1st1 8y ago
Thank you! Please share with us how it will go.
305.
by 1st1 8y ago
Thank you! > You either write them within strings, which sucks, because you lose all support from the editor (highlighting, auto-formatting, auto-suggestions, etc.), or you use an ORM, which I think is not a good solution to the problem.
306.
by 1st1 8y ago
EdgeDB is based on Postgres. There're ways of scaling it as Citus Data has shown, and there's a lot of ongoing work in PostgreSQL itself to improve the scalability. We'll be using that as well as actively contributing to fu
307.
by 1st1 8y ago
We want to provide high-quality bindings for other languages as soon as we can. In the meantime both EdgeQL and GraphQL can be exposed via an HTTP endpoint.
308.
by 1st1 8y ago
This goes a bit beyond what fits in a comment reply, but I'll try to be brief. - You can define a `bool` property as "optional" and then it can have an empty set as its value. - The 'exists' operator coverts sets in
309.
by 1st1 8y ago
> May I assume that the slight modifications you were required to make to postgres in order to support your features weren't just bug-fixes? Yes. Some of them, like strict parsing of timezone-aware vs naïve datetimes can be upstream
310.
by 1st1 8y ago
> An occasional post tracking the status of that upstreaming effort would be very welcome. We've already found a few bugs in Postgres and upstreamed fixes for them. There is a patch or two from us in their review pipeline right now
311.
by 1st1 8y ago
> Now you can't tell if it's empty or just not set. Those are the same things in EdgeDB. You can have a "required link", in which case a relationship between two objects is required, and therefore the link cannot eve
312.
by 1st1 8y ago
Key benefits: easier data model to deal with, integrated migrations, using EdgeQL (not SQL) to write advanced queries and expose them as GraphQL views. In the future we'll have integrated access control layer, but that's a subjec
313.
by 1st1 8y ago
> So this is basically a fork of Postgresql? Interesting. Why not just have an extension? EdgeQL as a language is so intuitive and advanced only because it operates on a very specific data model that can be compiled to a relational model
314.
by 1st1 8y ago
No. Some of the features required us to slightly modify Postgres, but we'll be trying to upstream the changes.
315.
by 1st1 8y ago
The main advantages are EdgeQL and the Data Model. EdgeQL is a fully featured query language, with support for subqueries, aggregation, transactions, rich datatypes like tuples/named tuples, arrays, JSON, etc. The Data Model is object-
316.
by 1st1 8y ago
> What is the minimal system requirements? Minimal requirements are similar to that of PostgreSQL. EdgeDB should run comfortably on an average server. > And what about partitioning, replication, event log, etc. Tooling for that will
317.
by 1st1 8y ago
Postgres is an amazing foundation to build on!
318.
by 1st1 8y ago
> I really like the re-imagination of the type system, data model, and the user interface. This is an area where databases could be significantly better than they currently are. Thank you! > Even on single machines, there is a perfor
319.
by 1st1 8y ago
EdgeDB is not a graph database, i.e. we didn't build it for traversing super deep schemaless graphs. On the contrary, we optimized it for the kind of applications that are usually built with relational or document databases. Those sce
320.
by 1st1 8y ago
Thank you :)
321.
by 1st1 8y ago
Thank you for your insightful comment! I agree, people do choose a database based on its track record, and this is where EdgeDB will have to prove itself. Overall, I think that the decision to build on PostgreSQL is a great competitive adv
322.
by 1st1 8y ago
Yes, it's linked from the article: https://github.com/edgedb/webapp-bench
323.
by 1st1 8y ago
Hello HN! This is a blog post about EdgeDB 1.0 Alpha 1. It's a new object-relational database, focused on type safety, usability, and developer ergonomics. We hope you will try it out!
324.
Show HN: EdgeDB – Next generation database(edgedb.com)
224 points by 1st1 8y ago|85 comments
325.
Immutability in Python(threadreaderapp.com)
3 points by 1st1 8y ago|0 comments
326.
by 1st1 8y ago
Jon, if you're looking for ideas what to work on next, please consider creating an email client. With fast UI & search, tree view for emails, proper support of plain text emails etc.
327.
by 1st1 8y ago
That's outdated info.
328.
by 1st1 8y ago
Who told you that? ;)
329.
by 1st1 8y ago
In Python 4.0 (the one after 3.9), and in Python 3.7 now with "from __future__ import annotations", annotations are parsed but their interpolation is delayed. So you can literally have "var: 0 < var < 3" (annotatio
330.
by 1st1 9y ago
You or somebody else must have subscribed your email address. We've never added any single email to our MailChimp list ourselves.

More ›