Through model for extra fields on M2M in Django - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a many-to-many relationship using a through model.

Django

class Book(models.Model):
    authors = models.ManyToManyField(Author, through=[1])

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

ABook

BBookAuthor

CAuthor

DAuthorBook

Attempts:

3 left

💡 Hint

Common Mistakes

Using the related model name instead of the through model.

Forgetting to define the through model class.

The through parameter should be the name of the intermediate model that holds extra fields.

2fill in blank

medium

Complete the through model with the correct field type for the foreign key to Book.

Django

class BookAuthor(models.Model):
    book = models.[1](Book, on_delete=models.CASCADE)

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

AForeignKey

BManyToManyField

COneToOneField

DCharField

Attempts:

3 left

💡 Hint

Common Mistakes

Using ManyToManyField inside the through model.

Using OneToOneField which restricts to one relation.

The through model uses ForeignKey fields to link to each related model.

3fill in blank

hard

Fix the error in the through model by completing the field for author.

Django

class BookAuthor(models.Model):
    author = models.[1](Author, on_delete=models.CASCADE)

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

AManyToManyField

BCharField

CForeignKey

DIntegerField

Attempts:

3 left

💡 Hint

Common Mistakes

Using CharField or IntegerField instead of ForeignKey.

Using ManyToManyField inside the through model.

The author field must be a ForeignKey to the Author model to link properly.

4fill in blank

hard

Fill both blanks to add an extra field and a string representation method in the through model.

Django

class BookAuthor(models.Model):
    book = models.ForeignKey(Book, on_delete=models.CASCADE)
    author = models.ForeignKey(Author, on_delete=models.CASCADE)
    [1] = models.IntegerField(default=0)

    def __str__(self):
        return f"[2] by [3] with contribution [1]%"

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

Acontribution

Bself.author

Cself.book

Dcontributor

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong field names or missing self in __str__ method.

Confusing attribute names.

The extra field is named contribution to store extra info. The string method uses self.book and self.author to show related objects.

5fill in blank

hard

Fill all three blanks to create a query that filters BookAuthor entries with contribution greater than 50.

Django

high_contrib = BookAuthor.objects.filter([1]__[2]=[3])

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

Acontribution

Bgt

C50

Dauthor

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong field names or lookup types.

Using single underscore instead of double underscore.

To filter by contribution greater than 50, use contribution__gt=50 in the filter.

Practice

1. What is the main purpose of using a through model in a Django many-to-many relationship?

easy

A. To avoid using foreign keys in models

B. To speed up database queries automatically

C. To create a one-to-one relationship instead

D. To add extra fields to the relationship between two models

Solution

1. Step 1: Understand many-to-many relationships

   A many-to-many field connects two models but by default stores only the link without extra data.

2. Step 2: Purpose of a through model

   A through model is a separate model that stores the connection plus extra fields about that connection.

3. Final Answer:

   To add extra fields to the relationship between two models -> Option D

4. Quick Check:

   Through model = extra fields on M2M [OK]

Hint: Through model = extra info on many-to-many link [OK]

Common Mistakes:

• Thinking through model speeds up queries
• Confusing through model with one-to-one relationships
• Believing through model removes foreign keys

2. Which of the following is the correct way to declare a many-to-many field using a through model named Membership in Django when the Membership model is defined later?

easy

A. members = models.ManyToManyField(User, through='Membership')

B. members = models.ManyToManyField(User, through=Membership())

C. members = models.ManyToManyField(User, through=Membership)

D. members = models.ManyToManyField(User, through='membership')

Solution

1. Step 1: Syntax for through argument

   The through argument expects the model name as a string if the model is defined later or in the same app.

2. Step 2: Correct usage

   Using 'Membership' as a string is correct. Passing the class or instance directly is incorrect.

3. Final Answer:

   members = models.ManyToManyField(User, through='Membership') -> Option A

4. Quick Check:

   through='ModelName' string syntax [OK]

Hint: Use model name as string in through argument [OK]

Common Mistakes:

• Passing model class or instance instead of string
• Using lowercase model name string
• Omitting the through argument

3. Given the models below, what will print(membership.role) output?

class Group(models.Model):
    name = models.CharField(max_length=100)

class User(models.Model):
    username = models.CharField(max_length=100)

class Membership(models.Model):
    user = models.ForeignKey(User, on_delete=models.CASCADE)
    group = models.ForeignKey(Group, on_delete=models.CASCADE)
    role = models.CharField(max_length=50)

# Usage
user = User(username='alice')
user.save()
group = Group(name='Developers')
group.save()
membership = Membership(user=user, group=group, role='admin')
membership.save()
print(membership.role)

medium

A. Error: role field missing

B. alice

C. admin

D. Developers

Solution

1. Step 1: Understand Membership model fields

   Membership has a role field storing a string like 'admin'.

2. Step 2: Check the saved membership instance

   Membership instance is created with role='admin', so printing membership.role outputs 'admin'.

3. Final Answer:

   admin -> Option C

4. Quick Check:

   membership.role = 'admin' [OK]

Hint: Print the extra field on through model instance [OK]

Common Mistakes:

• Confusing role with user or group fields
• Expecting username or group name instead
• Assuming role field is missing

4. What is wrong with this through model declaration?

class User(models.Model):
    username = models.CharField(max_length=100)

class Membership(models.Model):
    user = models.ForeignKey(User, on_delete=models.CASCADE)
    group = models.ForeignKey('Group', on_delete=models.CASCADE)
    role = models.CharField(max_length=50)

class Group(models.Model):
    name = models.CharField(max_length=100)
    members = models.ManyToManyField(User, through='Membership')

medium

A. Membership model is declared before Group, causing a NameError

B. No error; this is a valid declaration

C. The through model must be declared after both related models

D. ForeignKey fields in Membership must use related_name

Solution

1. Step 1: Check model declaration order

   Membership can be declared before Group if the through argument uses string 'Membership'.

2. Step 2: Validate through usage

   Using through='Membership' is correct and avoids circular import or NameError.

3. Final Answer:

   No error; this is a valid declaration -> Option B

4. Quick Check:

   through='ModelName' string allows any order [OK]

Hint: Use string name for through to avoid order errors [OK]

Common Mistakes:

• Thinking model order causes NameError with string through
• Believing related_name is mandatory for ForeignKey
• Assuming through model must be after both models

5. You want to track the date a user joined a group using a through model. Which of these is the best way to add this feature?

hard

A. Add a date_joined = models.DateField() field to the through model and use through='Membership' in the many-to-many field

B. Add a date_joined field directly to the User model

C. Add a date_joined field directly to the Group model

D. Use a signal to store the date_joined in a separate table unrelated to the many-to-many

Solution

1. Step 1: Identify where to store extra relationship data

   Extra info about the user-group link belongs in the through model, not in User or Group alone.

2. Step 2: Add date_joined field to through model

   Adding date_joined to Membership and linking with through='Membership' is the correct pattern.

3. Final Answer:

   Add a date_joined = models.DateField() field to the through model and use through='Membership' -> Option A

4. Quick Check:

   Extra data on M2M = through model field [OK]

Hint: Extra data on M2M? Put field in through model [OK]

Common Mistakes:

• Adding extra fields to User or Group instead of through model
• Using signals unnecessarily for simple data
• Not linking through model in many-to-many field