News for hackers. Stuff that matters.
Re:Prisma Raises $12M Series A by danpalmer on Friday June 26, 2020 @01:07PM (#23654287)
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?

Re:Prisma Raises $12M Series A by databrecht on Friday June 26, 2020 @05:12PM (#23657102)
Assuming 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
Re:Prisma Raises $12M Series A by fizx on Friday June 26, 2020 @03:47PM (#23656165)
I'm assuming that it's basically a port of GraphQL+DataLoader, so basically using recursive descent to manage hash joins.