Does the field mapper for prisma understand relationships? from my testing it seems not but just wanted to check if there is a workaround. So I have a field "request.resource.attr.authz.creatorId" which maps not to an intrinsic property of the model I am querying but to "authz.creatorId" where "authz" is a Prisma virtual field representing the 1:1 relationship between the models. So ideally I would pass a string with dot-notation as "authz.creatorId" but it seems like the query planner takes it literally and expects a column named like that to exist on the queried model.

There’s a

relationMapper

argument here that might solve what you need

Hey there is a 3rd parameter called

relationMapper

- there are some examples in the tests which are a starting point https://github.com/cerbos/query-plan-adapters/blob/main/prisma/src/index.test.ts#L455

What I am doing wrong here? "authz" is the Prisma virtual field that represents the 1:1 relation between the model I want to query and another table. The planner is producing these filters

{"authz.creatorId":{"equals":"userId"}}

when I would expect something like

{"authz": {"creatorId": {"equals": "userId"}}}

Hey @Norberto Cáceres can you share the relevent snippet of your prisma schema?

Here it is

thanks looking at this now

How come this is considered multiple relations? ApiKey is the resource I am trying to create a query plan for and it has a 1:1 with ApiKeyAuthz

Yeah I see what you after. Just to check is your prisma query would be something like this:

await prisma.ApiKey.findMany({
    where: { 
       authz: {
         creatorId: "..."
       }  
    },
  });

yes

Ok I think this PR should cover it https://github.com/cerbos/query-plan-adapters/pull/17

will do

Excellent. I’ll clean up the tests a bit and cut a proper release shortly

awesome, thanks

Prisms Extensions have just gone GA which might be a good fit for this