Bird
Raised Fist0
Flaskframework~30 mins

Relationships (one-to-many) in Flask - Mini Project: Build & Apply

Choose your learning style10 modes available
Flask One-to-Many Relationship Setup
📖 Scenario: You are building a simple blog application where each author can write many posts. You need to set up the data models to represent this one-to-many relationship using Flask and SQLAlchemy.
🎯 Goal: Create two Flask SQLAlchemy models named Author and Post where one author can have many posts. You will define the data structure, configure the relationship, and complete the model setup.
📋 What You'll Learn
Create an Author model with id and name fields
Create a Post model with id, title, and author_id fields
Set up a one-to-many relationship from Author to Post using SQLAlchemy
Use Flask-SQLAlchemy conventions and syntax
💡 Why This Matters
🌍 Real World
One-to-many relationships are common in web apps, like authors and their posts, customers and their orders, or teachers and their students.
💼 Career
Understanding how to model and implement relationships in databases is essential for backend development and working with ORMs like SQLAlchemy.
Progress0 / 4 steps
1
Create the Author model
Create a Flask SQLAlchemy model called Author with an integer primary key id and a string field name of length 50.
Flask
Hint

Use db.Column to define fields. The id should be an integer primary key. The name should be a string with max length 50.

2
Create the Post model with author_id
Create a Flask SQLAlchemy model called Post with an integer primary key id, a string field title of length 100, and an integer foreign key field author_id referencing author.id.
Flask
Hint

Use db.ForeignKey('author.id') to link author_id to the Author model's id.

3
Add relationship to Author model
Add a relationship property called posts to the Author model that links to the Post model using db.relationship with backref='author' and lazy=True.
Flask
Hint

Use db.relationship('Post', backref='author', lazy=True) inside the Author model.

4
Complete the model setup
Add the __repr__ method to both Author and Post models to return a string showing the name for Author and the title for Post.
Flask
Hint

Define __repr__ methods that return formatted strings with the model's main identifying field.

Practice

(1/5)
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
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard