FastAPI - Dependency Injection
You want to implement a FastAPI dependency that yields a database session and ensures it is closed after the request completes. Which implementation is correct?
You want to implement a FastAPI dependency that yields a database session and ensures it is closed after the request completes. Which implementation is correct?
hard🚀 Application Q8 of 15
Step-by-Step Solution
Solution:
Step 1: Understand resource management
Database sessions should be opened per request and closed after to avoid leaks.Step 2: Use generator dependencies
FastAPI supports dependencies as generators usingyieldto provide the resource and then run cleanup code after the request.Step 3: Correct pattern
Define a dependency function that creates the session, yields it, and then closes it after the yield.Final Answer:
Use a generator function with yield and close session after yield -> Option AQuick Check:
Yield dependencies allow cleanup after request [OK]
Quick Trick: Use yield in dependency to manage resource lifecycle [OK]
Common Mistakes:
MISTAKES- Not closing sessions leading to resource leaks
- Using global sessions causing concurrency issues
- Managing sessions manually inside path operations
Master "Dependency Injection" in FastAPI
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore FastAPI Quizzes