2 ms·
What exactly does your "query engine"/planner actually do? I understand the role that, for example, the Postgres query planner does. Is the idea that Prisma mi
by danpalmer 6y ago
What exactly does your "query engine"/planner actually do? I understand the role that, for example, the Postgres query planner does.
Is the idea that Prisma might be backing on to multiple databases and therefore needs another planning layer? If so, wouldn't this need to be very specific to the database and schema – knowing that particular fields in one database refer to entities in another? Does Prisma tackle this? How?
- fizx 6y agoI'm assuming that it's basically a port of GraphQL+DataLoader, so basically using recursive descent to manage hash joins.
- databrecht 6y agoAssuming something in the same vein as fizx with the addition that it's probably very similar to what Join Monster tries to solve: https://github.com/join-monster/join-monster https://github.com/join-monster/join-monster