3 ms·
> If you can't express something with EdgeQL that you can with SQL -- it's a bug. This is a huge promise. Especially with all the little "extra"s all different
by aljgz 5y ago
> If you can't express something with EdgeQL that you can with SQL -- it's a bug.
This is a huge promise. Especially with all the little "extra"s all different vendors have added. Love to read more.
One thing that separates EdgeDB from ORMs is the explicit design decision to be coupled with one specific database.
One more thing that can make me happy is to see if connection cost to EdgeDB is much lower than PostgreSql (one of the few architectural problems with PG).
Connecting only (or almost only) through EdgeDB fixes this one as a side effect.
- 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.
- RedCrowbar 5y ago> One thing that separates EdgeDB from ORMs is the explicit design decision to be coupled with one specific database. Yes, this is fundamental, and it is what enables us to drive the innovation in the query language. PostgreSQL's query engine is awesome and very powerful, but it is hopelessly obscured by SQL and its data model, and then further by the ORMs. EdgeDB and EdgeQL liberate that power and present it in a modernized way. EdgeQL wouldn't be possible or practical today without Postgres.