Relationships (one-to-many) in Flask - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a one-to-many relationship in Flask SQLAlchemy?

It means one record in a table can be linked to many records in another table. For example, one author can have many books.

beginner

How do you define a one-to-many relationship in Flask SQLAlchemy models?

Use db.relationship() on the "one" side and db.ForeignKey() on the "many" side to link tables.

intermediate

What does the backref parameter do in a one-to-many relationship?

It creates a shortcut to access the "one" side from the "many" side. For example, from a book, you can get its author easily.

intermediate

Why is it important to use lazy='dynamic' in relationships?

It delays loading related items until needed, which helps performance when you have many related records.

beginner

Show a simple example of a one-to-many relationship between Author and Book models in Flask SQLAlchemy.

class Author(db.Model):<br> &nbsp;&nbsp;id = db.Column(db.Integer, primary_key=True)<br> &nbsp;&nbsp;name = db.Column(db.String(50))<br> &nbsp;&nbsp;books = db.relationship('Book', backref='author', lazy='dynamic')<br><br>class Book(db.Model):<br> &nbsp;&nbsp;id = db.Column(db.Integer, primary_key=True)<br> &nbsp;&nbsp;title = db.Column(db.String(100))<br> &nbsp;&nbsp;author_id = db.Column(db.Integer, db.ForeignKey('author.id'))

In Flask SQLAlchemy, which side uses db.ForeignKey in a one-to-many relationship?

A Both sides

B The "many" side

C The "one" side

D Neither side

The "many" side holds the foreign key to link back to the "one" side.

What does the backref argument in db.relationship() create?

A A new table

B A validation rule

C A database index

D A shortcut to access the related object from the other side

It creates an easy way to access the related object from the opposite side of the relationship.

Which of these is a benefit of using lazy='dynamic' in relationships?

A Improves performance by loading related records only when needed

B Loads all related records immediately

C Prevents any related records from loading

D Automatically deletes related records

It delays loading related records until you ask for them, saving resources.

In a one-to-many relationship, how do you access all books of an author named author?

A author.get_books()

B author.book_id

C author.books

D author.books_id

The books attribute holds all related Book objects for that author.

What type of database column is used to link the 'many' side to the 'one' side?

A Foreign key

B Primary key

C Unique key

D Index

A foreign key column points to the primary key of the related table.

Explain how to set up a one-to-many relationship between two models in Flask SQLAlchemy.

Think about how one author can have many books and how to link them in code.

Describe the role of the 'lazy' parameter in Flask SQLAlchemy relationships and why it matters.

Consider how loading data only when needed helps your app run faster.

Practice

1. What does a one-to-many relationship in Flask SQLAlchemy represent?

easy

A. One record in a table is linked to many records in another table

B. Many records in a table are linked to one record in another table

C. Two tables have the same number of records

D. One record is linked to exactly one record in another table

Solution

1. Step 1: Understand the meaning of one-to-many

   One-to-many means one item in the first table relates to multiple items in the second table.

2. Step 2: Match the description to options

   One record in a table is linked to many records in another table correctly describes this relationship as one record linked to many records.

3. Final Answer:

   One record in a table is linked to many records in another table -> Option A

4. Quick Check:

   One-to-many = One record linked to many [OK]

Hint: One-to-many means one item connects to many items [OK]

Common Mistakes:

• Confusing one-to-many with many-to-one
• Thinking it means equal number of records
• Assuming one-to-many means one-to-one

2. Which of the following is the correct way to define a one-to-many relationship in Flask SQLAlchemy models?

easy

A. Both B and C together

B. child_id = db.Column(db.Integer, db.ForeignKey('parent.id'))

C. parent = db.relationship('Child', backref='parent', lazy=True)

D. db.relationship('Parent', foreign_key='child.id')

Solution

1. Step 1: Identify relationship and foreign key usage

   In Flask SQLAlchemy, one-to-many needs a relationship on the parent and a foreign key on the child.

2. Step 2: Check options for correct syntax

   parent = db.relationship('Child', backref='parent', lazy=True) shows the relationship on the parent, child_id = db.Column(db.Integer, db.ForeignKey('parent.id')) shows the foreign key on the child. Both are needed together.

3. Final Answer:

   Both B and C together -> Option A

4. Quick Check:

   Relationship + ForeignKey = Correct one-to-many [OK]

Hint: Use relationship on parent and ForeignKey on child [OK]

Common Mistakes:

• Defining only relationship without foreign key
• Using wrong foreign key syntax
• Confusing parent and child roles

3. Given these models, what will author.books return?

class Author(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    name = db.Column(db.String(50))
    books = db.relationship('Book', backref='author')

class Book(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    title = db.Column(db.String(100))
    author_id = db.Column(db.Integer, db.ForeignKey('author.id'))

# Assume author is an Author instance with 3 related Book records

medium

A. A single Book object

B. A list of Book objects related to the author

C. An integer count of books

D. null, because books is not defined

Solution

1. Step 1: Understand db.relationship returns

   The relationship attribute returns a list-like collection of related objects in one-to-many.

2. Step 2: Apply to author.books

   Since author.books is a relationship to Book, it returns a list of Book objects linked to that author.

3. Final Answer:

   A list of Book objects related to the author -> Option B

4. Quick Check:

   Relationship attribute returns list of related objects [OK]

Hint: Relationship attribute returns list of related items [OK]

Common Mistakes:

• Expecting a single object instead of a list
• Thinking it returns count instead of objects
• Assuming attribute is undefined

4. Identify the error in this Flask SQLAlchemy one-to-many setup:

class Parent(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    children = db.relationship('Child')

class Child(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    parent_id = db.Column(db.Integer)

medium

A. children should be a db.Column, not relationship

B. Relationship should be on Child, not Parent

C. Missing ForeignKey on Child's parent_id column

D. Parent model missing primary key

Solution

1. Step 1: Check Child model's parent_id column

   It lacks the ForeignKey constraint linking to Parent's id.

2. Step 2: Understand relationship requires ForeignKey

   Without ForeignKey, SQLAlchemy cannot link Child to Parent properly.

3. Final Answer:

   Missing ForeignKey on Child's parent_id column -> Option C

4. Quick Check:

   ForeignKey needed on child foreign key column [OK]

Hint: ForeignKey must be on child foreign key column [OK]

Common Mistakes:

• Forgetting ForeignKey on child side
• Placing relationship on wrong model
• Confusing relationship with column

5. You want to query all books written by an author named 'Alice' using Flask SQLAlchemy with one-to-many models Author and Book. Which code snippet correctly achieves this?

hard

A. author = Author.query.filter_by(name='Alice').all()\nbooks = author.books if author else []

B. books = Book.query.filter(author.name == 'Alice').all()

C. books = Book.query.filter_by(author='Alice').all()

D. books = Book.query.join(Author).filter(Author.name == 'Alice').all()

Solution

1. Step 1: Understand querying with relationships

   To filter books by author name, join Book with Author and filter by Author.name.

2. Step 2: Analyze options for correct query

   books = Book.query.join(Author).filter(Author.name == 'Alice').all() uses join and filter correctly to get all books by 'Alice'. author = Author.query.filter_by(name='Alice').all()\nbooks = author.books if author else [] accesses .books on list of authors (from .all()). books = Book.query.filter(author.name == 'Alice').all() uses invalid reference to 'author'. books = Book.query.filter_by(author='Alice').all() filters by author string incorrectly.

3. Final Answer:

   books = Book.query.join(Author).filter(Author.name == 'Alice').all() -> Option D

4. Quick Check:

   Use join and filter on related model for correct query [OK]

Hint: Use join and filter on related model for queries [OK]

Common Mistakes:

• Using .all() instead of .first() when accessing instance relationship
• Referencing related model without qualifier in filter
• Not joining tables before filtering