1st1

10 ms·

91.
Chit-chatting with EdgeDB docs via ChatGPT and pgvector(edgedb.com)
3 points by 1st1 3y ago|0 comments
92.
by 1st1 3y ago
> Analytic queries are not the primary intended use of EdgeQL You can write analytic queries with EdgeQL now, albeit we do need to add support of windowing. While we certainly prioritize usefulness of EdgeQL for the kind of efficient dat
93.
by 1st1 3y ago
EdgeDB is designed on the assumption that it fully controls and manages the underlying Postgres instance. This is why we can have a better/faster binary protocol, proper connection pooling on both client and server, and many many other
94.
by 1st1 3y ago
Yes it does :)
95.
by 1st1 3y ago
Both are on our list to start working on soon.
96.
by 1st1 3y ago
> I need window queries and subscriptions We'll get there.
97.
by 1st1 3y ago
We might support SQLite one day (not working on that right now, but there's some foundational work on that going on).
98.
by 1st1 3y ago
Huge thanks for the great feedback, I'm glad you're enjoying EdgeDB!
99.
by 1st1 3y ago
It's a reality, Posgres' analyze output wasn't designed for the plans that EdgeQL commands can have, given the composable nature of our language. You can just do much more in one op and that balloons the plan. Not in a bad wa
100.
by 1st1 3y ago
No, we think we should have it eventually but haven't started to work on it yet. Potentially we can create a C-wrapper for the Rust lib, which isn't ideal but might be doable in a shorter time frame.
101.
by 1st1 3y ago
Thanks!
102.
by 1st1 3y ago
Thank you!
103.
by 1st1 3y ago
> Will EdgeDB Cloud be fully replicated similar to https://neon.tech ? Eventually yes. Our client libraries APIs are designed in such a way that it's easy for us to automatically route read queries to the nearest replica
104.
by 1st1 3y ago
Hey, I'm Yury, CEO and co-founder here, eager to chat with you about EdgeDB.
105.
by 1st1 3y ago
Check out EdgeDB, you'll like it.
106.
by 1st1 3y ago
> This is like higher level and more readable + hopefully more efficient version of SQL. This.
107.
by 1st1 3y ago
All hot paths are in Rust or C, Postgres is the engine under the hood. Performance shouldn't be a big concern for you and will likely greatly surprise you: https://www.edgedb.com/blog/why-orms-are-slow-and-getting-
108.
by 1st1 3y ago
If you want graph algorithms -- not yet. If you want ability to easily work with hierarchical data to build apps--it's the best.
109.
by 1st1 3y ago
Give EdgeQL a try here, it will only take 5 minutes to get a taste of it: https://www.edgedb.com/tutorial Most likely you'll be surprised
110.
by 1st1 3y ago
We'll release one in a few weeks
111.
by 1st1 3y ago
Yes, coming in 3.0 in a few weeks.
112.
The Zen Side of the Moon(edgedb.com)
1 points by 1st1 3y ago|0 comments
113.
Bringing .NET to EdgeDB(edgedb.com)
4 points by 1st1 4y ago|0 comments
114.
EdgeDB and Dart(edgedb.com)
6 points by 1st1 4y ago|0 comments
115.
by 1st1 4y ago
Your comment on our Discord actually prompted an internal discussion on how we can implement this and we now have a pretty good idea. :) Not ETA or anything at this point, but we'll be looking into this soon.
116.
by 1st1 4y ago
Check out EdgeDB.
117.
by 1st1 4y ago
Build instructions: https://www.edgedb.com/docs/guides/contributing Repos: the first repo is the database itself; the second is our CLI -- tools for migrations, dump/restore, repl, etc.
118.
by 1st1 4y ago
EdgeDB stores data in a fairly normalized table layout, where every object type corresponds to a physical table. The performance of deep hierarchical queries with EdgeQL will be better than SQL with joins because with joins you'd have
119.
by 1st1 4y ago
I think you'll be able to use Django alright, but half of its value prop is their ORM and admin panel. Both of which you don't need with EdgeDB.
120.
by 1st1 4y ago
Not yet. Our reference documentation is extremely thorough though, an implementor of an alternative backend should be able to use it.

More ›