1st1

21 ms·

1. 271.▲
   EdgeDB 1.0 Alpha 3 “Proxima Centauri” with Rust inside(edgedb.com)

   3 points by 1st1 6y ago|0 comments
2. 272.▲
   by 1st1 7y ago

   Really sorry for everyone affected. EdgeDB Inc (of which I'm the CEO) is hiring. We're well funded early stage startup with a mission to build the next generation database. We're looking for engineers with extensive knowledge
3. 273.▲
   by 1st1 7y ago

   Here's a benchmark [1] against aiopg, which is psycopg2+asyncio. [1] http://magic.io/blog/asyncpg-1m-rows-from-postgres-to-python...
4. 274.▲
   EdgeDB 1.0 Alpha 2(edgedb.com)

   6 points by 1st1 7y ago|0 comments
5. 275.▲
   PEP 603: Adding persistent mapping type to Python(python.org)

   3 points by 1st1 7y ago|0 comments
6. 276.▲
   by 1st1 7y ago

   I'm an EdgeDB co-founder, happy to answer any questions! EdgeDB is a new relational database based on Postgres with native support for GraphQL.
7. 277.▲
   EdgeDB Roadmap(edgedb.com)

   6 points by 1st1 7y ago|1 comments
8. 278.▲
   EdgeDB: A Path to a 10x Database(edgedb.com)

   8 points by 1st1 7y ago|0 comments
9. 279.▲
   by 1st1 7y ago

   I wish we "flop" like MongoDB :)
10. 280.▲
    by 1st1 7y ago

    The point of that blog post is to look at both performance and usability. MongoDB has a way to fetch data the way we needed and the way other databases fetch it in our benchmarks. We tried just that: the performance is roughly the same any
11. 281.▲
    by 1st1 7y ago

    I think that EdgeDB actually addresses a lot of your comments re "General ugliness of server-side SQL", i.e. [ ] You cannot parametrize ORDER BY, GROUP BY, IN... [v] type inference [v] tuples, tuples of tuples, arrays of tuples, a
12. 282.▲
    by 1st1 7y ago

    Thank you for your comment, it aligns pretty well with our current thinking about this. > It could also be cool to explore interoperation with existing schemas written in plain SQL, so people could adopt it incrementally that way. Yes, t
13. 283.▲
    by 1st1 7y ago

    The comment in the query mentions that it makes the query only 5% slower. You can drop the "full_name" part, but the query would be still too low level (even compared to SQL/ORM examples) and slow.
14. 284.▲
    by 1st1 7y ago

    Exactly. The situation is even worse because many libraries support only "common ground of SQL" and therefore underutilize the real capabilities of the database. We mentioned that there are "many SQLs" in this blog post
15. 285.▲
    by 1st1 7y ago

    You can use the EXISTS operator: https://edgedb.com/docs/edgeql/funcops/set#operator::EXISTS
16. 286.▲
    by 1st1 7y ago

    > And do you support other backends as well (i.e. MySQL?). Does EdgeDB still offer a regular SQL interface because people need time to migrate. No, but we have a few ideas on how to connect existing databases to EdgeDB. > Even if I wa
17. 287.▲
    by 1st1 7y ago

    Quite a big number, but probably not all yet. For example, in one of the future releases we'll add support for GIS types.
18. 288.▲
    by 1st1 7y ago

    JavaScript and Go clients are coming soon. Java/Rust will follow.
19. 289.▲
    by 1st1 7y ago

    Latest stable and we'll keep it that way.
20. 290.▲
    by 1st1 7y ago

    Actually quite a lot of people told us they thought EdgeQL was inspired by Tutorial D :) Have you had a chance to actually try to play with EdegQL?
21. 291.▲
    by 1st1 7y ago

    Yes, we are not debating that.
22. 292.▲
    by 1st1 7y ago

    This is exactly what we do. EdgeDB is based on PostgreSQL.
23. 293.▲
    by 1st1 7y ago

    We think that people struggling with writing good/advanced SQL queries and the existence of ORMs and other heavy frameworks to make RDBMSes "friendly" is a serious problem. And inventing a a new querying language is a necess
24. 294.▲
    by 1st1 7y ago

    > don't use NULL I'm not sure this part is realistic to do in a non-trivial setup. At the very least it's not a common thing to do.
25. 295.▲
    by 1st1 7y ago

    > Even replacing some of the UPPERCASE words in SQL with C-like symbols would be nice. In EdgeQL the keywords are recognized in any case. It is a matter of personal style.
26. 296.▲
    by 1st1 7y ago

    > [..] SQL is typed and has a ton of historical overhead [..] EdgeQL is strictly typed, here's more info: https://edgedb.com/docs/edgeql/overview/ > slightly different implementation of NoSQL synta
27. 297.▲
    by 1st1 7y ago

    Yeah, it's because it is new. We released the first public version a few weeks ago, here's a blog post with the announcement: https://edgedb.com/blog/edgedb-1-0-alpha-1 Hope you will try it!
28. 298.▲
    We Can Do Better Than SQL(edgedb.com)

    624 points by 1st1 7y ago|424 comments
29. 299.▲
    by 1st1 8y ago

    You can do this in EdgeDB. The fact that the data is normalized doesn't really matter, because you can request it as JSON.
30. 300.▲
    by 1st1 8y ago

    Yes, we will have it (via abstracted away PostGIS)