FranzaLeny
Results
1
comments of
FranzaLeny
In this code:   This bug occurs because PrismaClient version 6.0.0 is treated the same as PrismaClient version 5.0.x or earlier.