1st1

11 ms·

1. 121.▲
   by 1st1 4y ago

   > The declarative composable query language is a paradigm shift imo — not just a better ORM. This!
2. 122.▲
   by 1st1 4y ago

   Yeah, that's the dream. But there are lots of tiny details to figure out to make it really usable in prod and not gimmicky. Hasura is a great product indeed.
3. 123.▲
   by 1st1 4y ago

   We use it throughout our UI in all interactive elements. It's super annoying when, say, a button or a navigation element gets accidentally selected for no reason.
4. 124.▲
   by 1st1 4y ago

   We'll have that in 3.0; we're shooting for a more advanced splat-like syntax. Simple * wouldn't cut it because one of the principals of EdgeQL is to fetch only what you need, aiming for efficiency. That said, our UI repl has
5. 125.▲
   by 1st1 4y ago

   Thanks! Depends on what kind of frameworks you like. EdgeDB+Next.js or EdgeDB+Flask are very pleasant to use already. But there's no heavyweight one like Django or RoR just yet.
6. 126.▲
   by 1st1 4y ago

   The Go client implements the full client API, but yeah, it lacks the query building capability. We want all of our client APIs to have it; it's a matter of time, but I don't have a concrete ETA on when we get to it. Hopefully in t
7. 127.▲
   by 1st1 4y ago

   Finally somebody compliments that! Jokes aside, thank you!
8. 128.▲
   by 1st1 4y ago

   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:
9. 129.▲
   by 1st1 4y ago

   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
10. 130.▲
    by 1st1 4y ago

    Thanks! I think most people dread working with complicated SQL queries, especially experienced DBAs :)
11. 131.▲
    by 1st1 4y ago

    Thank you! Yeah, we spent significant amount of effort making the syntax of EdgeQL logical and predictable. Most of the time, queries can be read from top to bottom easily, even when you don't know EdgeQL.
12. 132.▲
    by 1st1 4y ago

    Yeah. Also behind uvloop :blush:
13. 133.▲
    by 1st1 4y ago

    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.
14. 134.▲
    by 1st1 4y ago

    Thanks!
15. 135.▲
    by 1st1 4y ago

    Yes, we're building that capability. With 2.0 we made our protocol stateless and can tunnel it through HTTP now, allowing access to full APIs of our clients. (Although EdgeDB also exposes a REST endpoint that you can access with any HT
16. 136.▲
    by 1st1 4y ago

    > There would also be some friction as to having to learn this new ORM language and having to rely on it completely whereas if we just stick to SQL and traditional ORM that is more popular (SQLAlchemy and SQLModel) You'll be surpris
17. 137.▲
    by 1st1 4y ago

    Thanks!
18. 138.▲
    by 1st1 4y ago

    Would really appreciate it if you could open issues in the main [1] repo and we'll figure it out. We're investing a ridiculous amount of time into our docs and want them to be the best possible. [1] https://github.com&#
19. 139.▲
    by 1st1 4y ago

    I'll check CodeQL out, thanks!
20. 140.▲
    by 1st1 4y ago

    Yeah, that will all be simplified when we launch our cloud. Our goal is to make it possible to deploy to cloud with one short cli command. We'll have it soon.
21. 141.▲
    by 1st1 4y ago

    Obviously :)
22. 142.▲
    by 1st1 4y ago

    The fix will be up in a few minutes :)
23. 143.▲
    by 1st1 4y ago

    Thank you, we'll keep pushing! :)
24. 144.▲
    by 1st1 4y ago

    We'll be closely looking an Neon and we know the team. There are some related things that we have to figure out before investing time into the integration.
25. 145.▲
    by 1st1 4y ago

    We don't have that yet. Maybe it will be possible to bootstrap EdgeDB to run on top of SQLite, but that will be a ton of work and limit the schema/language. Nothing prevents you from just running EdgeDB or even bundling in your ap
26. 146.▲
    by 1st1 4y ago

    Just a side note: EdgeDB doesn't implement OOP persistence, so it's not an classical object database.
27. 147.▲
    by 1st1 4y ago

    Thanks! > is that it seems quite strict on schema ? Yes, it is. But you can use JSON in your schema, we have amazing support for it on all levels (the query language, std library, schema integration, client APIs, etc).
28. 148.▲
    by 1st1 4y ago

    We'll be working on (3) soon and maybe (2) shortly after.
29. 149.▲
    by 1st1 4y ago

    Wow, that's one great dashboard. Thanks for sharing.
30. 150.▲
    by 1st1 4y ago

    EdgeDB is super efficient in its communication with the postgres backend. Most of the time there's only one roundtrip for any query. So chances are, because of how you can pipeline many operations in EdgeQL into one single query, the l