Mykyta Machekhin
04/26/2022, 8:47 AMJared Fraser
04/26/2022, 9:02 AMMykyta Machekhin
04/26/2022, 9:06 AMJared Fraser
04/26/2022, 9:17 AMtaskId
on the aggr_selection_2_Task
table?Mykyta Machekhin
04/26/2022, 10:35 AMtaskId
field
For explain why, I attach screen with query from log, when Prisma run my query:
So MediaFile
table is table from I select count of nested entities. _resultMediaFiles
is internal entities. which Prisma generate automaticly, based on my relation many to many between entities MediaFile
and Task
. So, table _resultMediaFiles
has only A
and B
fields (respectively ids from nested entities – MediaFile
and Task
). And taskId
is only in Task
entity, which Prisma dont select at all in its query. So I don’t understand why the Prisma in runtime thinks that this field must existMykyta Machekhin
04/26/2022, 1:27 PMNurul
04/26/2022, 2:05 PMMykyta Machekhin
04/26/2022, 2:10 PMMykyta Machekhin
04/26/2022, 2:13 PMTask
. Mb it can be useful.I highlighted the relationships that we are interested inJared Fraser
04/27/2022, 1:40 AMMykyta Machekhin
04/27/2022, 9:55 AMtaskId
exist in the table Task
. But not exist in MediaFile JOIN _resultMediaFiles
, from which Prisma try to select itJared Fraser
04/27/2022, 11:22 PMMykyta Machekhin
04/28/2022, 11:25 AMNurul
05/04/2022, 3:10 PMMykyta Machekhin
05/04/2022, 7:48 PM