Yiming Cao

Hi @israelins85 , I had a try but couldn't reproduce this issue with v2.2.3. I've shared a project here: https://github.com/ymc9/issue-1519 Could you check what differences it may have with your...

> Hey, I'm having same issue. > > Example of such model would be: > > ``` > model Space { > id String @id @default(cuid()) > createdAt DateTime @default(now())...

Sorry I missed your reply @igorsimko . I'll check it and update back here.

This is a tricky problem ... The root comes from the fact that Prisma doesn't support comparing fields from different tables. For example, in the rule in https://github.com/igorsimko/issue-1519/blob/main/schema.zmodel: ```prisma model...

Btw, there's actually a check in ZenStack's validator that should capture comparisons between different models and report an error ... However your rules somehow didn't get caught by the check....

> @israelins85 thanks for suggestion again, but this is very error prone and it makes then whole zenstack need for this use case redundant. Only thing I can think of...

Sorry I was clear in the previous comment. What I meant was for this specific rule: ```prisma model SpaceEnvironmentBot { id String @id @default(cuid()) createdAt DateTime @default(now()) updatedAt DateTime @updatedAt...

I'm afraid there's no way to express this with Prisma either ... considering it needs to be transformed into a where filter like: ```ts prisma.spaceEnvironmentBot.findMany({ where: { environmentId: { in:...

> ``` > prisma.spaceEnvironmentBot.findMany({ > where: { > environment: { userAccess: { some: { userId: auth.userId } } }, > spaces: { userAccess: { some: { userId: auth.userId, environment: {...

> > I'm not sure how much time you have to continue working on this. Another option is we merge it first, and I can follow up with a separate...