NestJS - Database with TypeORM
Why does NestJS recommend using the transaction method on DataSource instead of manually managing query runners for transactions?
Why does NestJS recommend using the transaction method on DataSource instead of manually managing query runners for transactions?
hard📝 Conceptual Q10 of 15
Step-by-Step Solution
Solution:
Step 1: Understand DataSource.transaction benefits
It abstracts transaction management, ensuring connections are released and rollbacks happen on errors automatically.Step 2: Evaluate other options
Manual query runners are supported but require more code. The other options are incorrect.Final Answer:
It automatically handles connection release and rollback on errors -> Option CQuick Check:
DataSource.transaction simplifies transaction management [OK]
Quick Trick: Use DataSource.transaction for safe, automatic transaction handling [OK]
Common Mistakes:
- Believing manual query runners are deprecated
- Thinking DataSource.transaction disables logging
- Assuming manual query runners can't run multiple queries
Master "Database with TypeORM" in NestJS
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore NestJS Quizzes