Benjamin Zecirovic
Benjamin Zecirovic
> Prisma version: 5.13.0 > Database type: Postgresql But I tested all releases. The bug was introduced in v2.0.0.
> Hi @iamfj @baenie , could you try if the new 2.1.1 release fixed the issue? It seams to work now! Thank you for your fast response! ❤️
Great suggestion! 🎉 I completely agree - as the schema grows, the generation time increases significantly, which can be quite a bottleneck. Implementing a caching mechanism would be a game-changer...
Thank you @ymc9 for your response! I really like the idea of having a generic extensibility with custom functions for the access control! This could help making it as secure...
`@createdBy` is not necessary, because neither Prisma is having it - using `@default(auth().id)` is already very nice
Thanks a lot for the detailed follow-up, @jiashengguo — and no worries at all! I really appreciate you taking the time to investigate this and explain the reasoning behind it....