Why ORM simplifies database access in Flask - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does ORM reduce manual SQL writing?

Which of the following best explains how ORM simplifies database access in Flask applications?

A ORM only works with NoSQL databases, making SQL unnecessary.

B ORM automatically converts Python objects to SQL queries, so developers write less raw SQL code.

C ORM replaces the need for a database by storing data in Python files.

D ORM requires developers to write SQL queries manually but organizes them better.

💡 Hint

Think about how ORM handles data between Python and the database.

ORM (Object-Relational Mapping) lets developers work with Python objects instead of writing SQL queries directly. It translates Python code into SQL behind the scenes, reducing manual SQL writing.

❓ component_behavior

intermediate

What happens when you add a new object with ORM?

In Flask with SQLAlchemy ORM, what happens when you create a new object, add it to the session, and then commit?

Flask

new_user = User(name='Alice')
session.add(new_user)
session.commit()

A A new row is inserted into the users table with name 'Alice'.

B The new_user object is saved only in Python memory and not in the database.

C An error occurs because commit() is missing.

D The users table is deleted and recreated.

💡 Hint

Consider what session.commit() does in ORM.

Adding an object to the session and committing saves it to the database as a new row. The ORM handles the SQL INSERT automatically.

📝 Syntax

advanced

Identify the correct ORM query syntax

Which option correctly queries all users with age greater than 30 using Flask SQLAlchemy ORM?

Flask

users = User.query.filter(User.age > 30).all()

A users = User.query.where(User.age > 30).get()

B users = User.query.filter_by(age > 30).all()

C users = User.query.filter(User.age > 30).all()

D users = User.query.filter(User.age > 30)

💡 Hint

Remember the difference between filter and filter_by methods.

filter() accepts expressions like User.age > 30, while filter_by() only accepts keyword arguments. Also, .all() returns all matching results.

🔧 Debug

advanced

Why does this ORM code raise an error?

Given the code below, which of the following is correct? user = User(name='Bob') session.add(user) session.commit() print(user.id)

Flask

user = User(name='Bob')
session.add(user)
session.commit()
print(user.id)

A The user.id is available after commit because ORM updates the object with the database id.

B AttributeError occurs because the User model has no id attribute defined.

C The user.id is None because the session was not flushed before commit.

D The code raises an error because commit() must be called before add().

💡 Hint

Think about how ORM handles primary keys after saving.

After commit(), ORM updates the user object with the generated primary key id from the database, so user.id is accessible.

❓ state_output

expert

What is the output after modifying an ORM object before commit?

Consider this Flask SQLAlchemy code: user = User(name='Carol', age=25) session.add(user) user.age = 26 session.commit() print(user.age) What will be printed?

Flask

user = User(name='Carol', age=25)
session.add(user)
user.age = 26
session.commit()
print(user.age)

A Raises an error because age was changed after add()

B 25

C None

D 26

💡 Hint

Think about how ORM tracks changes before commit.

ORM tracks changes to objects in the session. Changing user.age before commit updates the database and the object, so printing user.age shows 26.