NestJS - Database with PrismaWhy does Prisma require explicit foreign key fields and @relation attributes in relations instead of inferring them automatically?ATo force developers to write more codeBTo clearly define relation direction and keys for database consistencyCBecause Prisma does not support relations without explicit keysDBecause implicit relations cause runtime errors alwaysCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand Prisma relation designExplicit foreign keys and @relation attributes clarify how models connect and which fields link them.Step 2: Reason why explicit definitions matterThis ensures database consistency, avoids ambiguity, and helps Prisma generate correct queries and migrations.Final Answer:To clearly define relation direction and keys for database consistency -> Option BQuick Check:Explicit keys ensure clear, consistent relations [OK]Quick Trick: Explicit keys clarify relation direction and consistency [OK]Common Mistakes:Thinking Prisma infers all relations automaticallyBelieving explicit keys are optionalAssuming implicit relations never cause issues
Master "Database with Prisma" in NestJS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallPerf
More NestJS Quizzes Database with Prisma - Prisma migrations - Quiz 1easy Database with Prisma - CRUD with Prisma - Quiz 8hard Database with TypeORM - Relations (OneToMany, ManyToOne, ManyToMany) - Quiz 1easy Guards - JWT authentication guard - Quiz 14medium Guards - Guard interface (canActivate) - Quiz 11easy Guards - Role-based guards - Quiz 15hard Interceptors - Why interceptors add cross-cutting logic - Quiz 9hard Middleware - Applying middleware to routes - Quiz 8hard Pipes - Built-in pipes (ParseIntPipe, ParseBoolPipe) - Quiz 4medium Pipes - ValidationPipe in depth - Quiz 9hard