Hacker News Reader

I don’t think you can call Prisma a “query builder”…

It introduces its own global DSL for describing relationships between tables, and then you query that. So if you need a relationship for any query, it’s now present in the model for every query. That doesn’t feel like a query builder to me.

A query builder should still look like the SQL if you blur your eyes. Prisma does not.

View on HN

A different view on this is that relationships is a property of the data, not of the query. So it makes sense to represent that in a single place instead of repeating it for every query. Now, if multiple teams have differing understandings of what relationships are present in the data, they can go ahead and use separate Prisma Schemas.

Reply on news.ycombinator.com