Nonetheless, great to see a new serious Go meta framework.
It’s not a Graph DB under the hood and uses any normal relational db quite normally beneath the DX
I’m specifically talking about this: 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.
On the one hand, it's a very comprehensive ORM (support for different DBs and types of queries, joins, associations, etc). On the other hand, the documentation is not very good and often its behavior leaves you baffled (updates of columns and the associates in different times, for example).
Overall, I think I'd still choose an ORM over writing SQL or quasi-SQL in the code for the sake of maintainability and readability of the code. GORM is the best one around but I wish there were more options.