Why ORM simplifies database access in Flask - Quick Recap

Recall & Review

beginner

What does ORM stand for and what is its main purpose?

ORM stands for Object-Relational Mapping. Its main purpose is to let developers work with databases using simple code objects instead of writing complex SQL queries.

beginner

How does ORM help avoid writing raw SQL in Flask applications?

ORM lets you use Python classes and methods to create, read, update, and delete data. This means you don't have to write SQL commands manually, making code easier and less error-prone.

intermediate

Explain how ORM improves code readability and maintenance.

ORM uses clear Python code that looks like working with normal objects. This makes the code easier to read and maintain compared to mixing SQL strings inside your code.

intermediate

What is one way ORM handles differences between database systems?

ORM abstracts the database details so you can switch databases (like SQLite to PostgreSQL) without changing much code. It translates your Python commands into the right SQL for each database.

intermediate

Why is ORM considered safer when dealing with user input?

ORM helps prevent SQL injection attacks by automatically handling user input safely. It builds queries in a way that avoids dangerous code execution.

What is the main benefit of using ORM in Flask?

A Make the website load faster

B Write database queries using Python objects instead of SQL

C Automatically create HTML pages

D Replace Flask routing system

ORM lets you interact with the database using Python objects, avoiding manual SQL.

How does ORM improve code safety?

A By preventing SQL injection attacks

B By speeding up the server

C By encrypting all data automatically

D By disabling user input

ORM safely handles user input to avoid SQL injection vulnerabilities.

Which of these is NOT a feature of ORM?

A Automatically translating Python code to SQL

B Allowing switching between different databases easily

C Generating CSS styles for the app

D Making code easier to read and maintain

ORM does not handle CSS or styling; it focuses on database access.

What does ORM map between?

A Flask routes and URLs

B HTML and CSS

C JavaScript and Python

D Python objects and database tables

ORM connects Python objects with database tables to simplify data handling.

Why might a developer choose ORM over raw SQL?

A To write less complex and more readable code

B To avoid using Python

C To make the app run offline

D To create mobile apps

ORM reduces complexity by letting developers use Python code instead of raw SQL.

Describe in your own words how ORM simplifies working with databases in Flask.

Think about how ORM changes the way you write database code.

List three advantages of using ORM in a web application.

Focus on benefits related to coding, security, and flexibility.

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