3 ms·
Ent heavily uses joins and does support multi field indices, you should read up on the docs. You can show the queries it’s running using a debug client. It’s n
by endigma 2y ago
Ent heavily uses joins and does support multi field indices, you should read up on the docs. You can show the queries it’s running using a debug client.
It’s not a Graph DB under the hood and uses any normal relational db quite normally beneath the DX
- ko_pivot 2y ago> Ent heavily uses joins I’m specifically talking about this: https://github.com/ent/ent/issues/977 https://github.com/ent/ent/issues/977. Devs assume that the `With` methods are adding join clauses but that is not typically the case. > does support multi field indices Composite primary keys are useful for reasons other than unique constraints and query speed. For example, CockroachDB uses the primary key to partition rows. Also, at scale, an extra multi-column index in addition to the primary key when the primary key alone could have sufficed can be a meaningful performance degradation. > not a Graph DB under the hood No it is not, but because it has a graph ‘mindset’ and does support Gremlin, traditional SQL folks expecting a lightweight ORM (such as Drizzle in the JS world) may not have a good time.