[Solved] Given the following Flask-SQLAlchemy code, what happens when print(user.posts) is executed?user = User.query.first() print(user.posts)Assuming posts relationship is defined with lazy='select'. | Flask

Flask - Performance Optimization

Given the following Flask-SQLAlchemy code, what happens when print(user.posts) is executed?

user = User.query.first()
print(user.posts)

Assuming posts relationship is defined with lazy='select'.

AAn error occurs because posts are not loaded.

BPosts are already loaded with the user in the first query.

CA separate query is executed to load posts when accessed.

DPosts are never loaded and print shows empty list.

Step-by-Step Solution

Solution:

Step 1: Understand lazy='select' behavior
With lazy='select', related posts are not loaded initially but fetched when accessed.
Step 2: Analyze code execution
When print(user.posts) runs, it triggers a separate query to load posts.
Final Answer:
A separate query is executed to load posts when accessed. -> Option C
Quick Check:
lazy='select' triggers query on access [OK]

Quick Trick: lazy='select' loads related data on attribute access [OK]

Common Mistakes:

MISTAKES

Master "Performance Optimization" in Flask

9 interactive learning modes - each teaches the same concept differently

More Flask Quizzes

Given the following Flask-SQLAlchemy code, what happens when print(user.posts) is executed?