Why ORM simplifies database access in Flask - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the ORM base class from SQLAlchemy.

Flask

from flask_sqlalchemy import [1]

Drag options to blanks, or click blank then click option'

ADatabase

BFlask

CSQLAlchemy

DModel

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Flask' instead of 'SQLAlchemy' will cause import errors.

The SQLAlchemy class is the base for ORM in Flask. It helps connect Python classes to database tables.

2fill in blank

medium

Complete the code to define a model class for a user table.

Flask

class User(db.[1]):

Drag options to blanks, or click blank then click option'

AModel

BTable

CBase

DEntity

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Table' or 'Base' will cause errors because they are not the correct base class.

The Model class is the base class for all ORM models in Flask-SQLAlchemy.

3fill in blank

hard

Fix the error in the column definition to specify a primary key.

Flask

id = db.Column(db.Integer, [1]=True)

Drag options to blanks, or click blank then click option'

Amain_key

Bprimary

Ckey_primary

Dprimary_key

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'primary' or 'key_primary' will cause runtime errors.

The correct keyword argument to mark a column as primary key is primary_key=True.

4fill in blank

hard

Fill both blanks to create a query that gets all users with age greater than 18.

Flask

adults = User.query.filter(User.age [1] [2]).all()

Drag options to blanks, or click blank then click option'

A>

B18

C<

D21

Attempts:

3 left

💡 Hint

Common Mistakes

Using '<' or 21 will give wrong results or no results.

The filter uses the greater than operator '>' and the value 18 to get adult users.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps usernames to emails for users older than 20.

Flask

user_dict = {user.[1]: user.[2] for user in users if user.[3] > 20}

Drag options to blanks, or click blank then click option'

Ausername

Bemail

Cage

Did

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'id' instead of 'username' or wrong filter attribute causes errors.

The comprehension uses 'username' as key, 'email' as value, and filters users with 'age' greater than 20.

Practice

1. Why does using an ORM in Flask make working with databases easier?

easy

A. Because it only works with one type of database

B. Because it requires writing more SQL code manually

C. Because it lets you use Python objects instead of writing SQL queries directly

D. Because it removes the need to understand databases at all

Solution

1. Step 1: Understand ORM purpose

   ORM stands for Object-Relational Mapping, which connects Python classes to database tables.

2. Step 2: Identify how ORM simplifies work

   It lets you use Python objects to create, read, update, and delete data without writing SQL queries manually.

3. Final Answer:

   Because it lets you use Python objects instead of writing SQL queries directly -> Option C

4. Quick Check:

   ORM uses Python objects, not raw SQL [OK]

Hint: Think: ORM means Python objects replace SQL queries [OK]

Common Mistakes:

• Thinking ORM requires more SQL code
• Believing ORM only supports one database
• Assuming ORM removes all database knowledge needs

2. Which of the following is the correct way to define a model class using Flask's ORM (SQLAlchemy)?

easy

A. class User: id = Column(Integer, primary_key=True)

B. def User(): id = Column(Integer, primary_key=True)

C. User = db.Model(id = Column(Integer, primary_key=True))

D. class User(db.Model): id = db.Column(db.Integer, primary_key=True)

Solution

1. Step 1: Recall Flask SQLAlchemy model syntax

   Models inherit from db.Model and define columns with db.Column and types like db.Integer.

2. Step 2: Check each option

   class User(db.Model): id = db.Column(db.Integer, primary_key=True) correctly defines a class inheriting db.Model with a column using db.Column and db.Integer.

3. Final Answer:

   class User(db.Model): id = db.Column(db.Integer, primary_key=True) -> Option D

4. Quick Check:

   Model class inherits db.Model and uses db.Column [OK]

Hint: Model classes inherit db.Model and use db.Column for fields [OK]

Common Mistakes:

• Not inheriting from db.Model
• Using Column without db prefix
• Defining model as a function instead of class

3. Given this Flask ORM code:

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

What will print(user.id) output after commit?

medium

A. The new unique ID assigned by the database

B. None

C. An error because id is not set

D. The string 'Alice'

Solution

1. Step 1: Understand ORM session commit behavior

   When you add and commit a new object, the database assigns a unique ID (primary key) automatically.

2. Step 2: Check what user.id holds after commit

   After commit, ORM updates the object with the assigned ID, so user.id contains that new value.

3. Final Answer:

   The new unique ID assigned by the database -> Option A

4. Quick Check:

   Commit assigns and updates object ID [OK]

Hint: After commit, ORM sets the object's ID from the database [OK]

Common Mistakes:

• Expecting id to be None before commit
• Thinking id is the name value
• Assuming commit does not update object fields

4. What is wrong with this Flask ORM code snippet?

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

medium

A. It will print None because commit is missing

B. It will raise a syntax error

C. It will print the name instead of id

D. It will print a random number

Solution

1. Step 1: Identify missing commit

   The code adds the user to the session but does not commit, so the database does not assign an ID yet.

2. Step 2: Understand user.id value before commit

   Before commit, user.id is None because the database has not generated the primary key.

3. Final Answer:

   It will print None because commit is missing -> Option A

4. Quick Check:

   Commit needed to assign ID [OK]

Hint: Remember to commit to get database-generated IDs [OK]

Common Mistakes:

• Forgetting to call commit() after add()
• Expecting id to be set immediately after add()
• Confusing id with other attributes

5. You want to update a user's email in Flask ORM. Which approach best shows how ORM simplifies this compared to raw SQL?

user = User.query.filter_by(id=5).first()
user.email = '[e-mail]'
db.session.commit()

Why is this simpler than writing SQL?

hard

A. Because you must write raw SQL inside the Python code

B. Because you update the Python object directly without writing an UPDATE SQL statement

C. Because ORM automatically commits changes without calling commit()

D. Because you still need to write the full SQL UPDATE query manually

Solution

1. Step 1: Understand ORM object update

   You fetch the user as a Python object, change its attribute, and commit the session.

2. Step 2: Compare with raw SQL

   Raw SQL requires writing an UPDATE statement manually, but ORM lets you work with objects and attributes directly.

3. Final Answer:

   Because you update the Python object directly without writing an UPDATE SQL statement -> Option B

4. Quick Check:

   ORM updates objects, no manual SQL needed [OK]

Hint: ORM lets you change objects, not write SQL queries [OK]

Common Mistakes:

• Thinking ORM requires manual SQL for updates
• Assuming commit() is automatic
• Believing raw SQL is simpler than ORM