Inline models for related data in Django - Mini Project: Build & Apply

Inline models for related data

📖 Scenario: You are building a simple Django admin interface for a bookstore. Each Book can have multiple Authors. You want to manage the authors directly on the book's admin page using inline models.

🎯 Goal: Create Django models for Book and Author with a relationship. Then configure the Django admin to show Author as an inline model on the Book admin page.

📋 What You'll Learn

Create a Django model called Book with a title field.

Create a Django model called Author with a name field and a foreign key to Book.

Create an inline admin class for Author using TabularInline.

Register the Book model in the admin with the Author inline.

💡 Why This Matters

🌍 Real World

Managing related data like authors for books directly in the admin page saves time and keeps data organized.

💼 Career

Knowing how to use inline models in Django admin is a common task for backend developers working with Django to build admin interfaces.

1

Create the Book and Author models

Create a Django model called Book with a title field as models.CharField(max_length=100). Also create a Django model called Author with a name field as models.CharField(max_length=50) and a foreign key to Book named book with on_delete=models.CASCADE.

Django

# Your code here

Hint

Use models.CharField for text fields and models.ForeignKey to link Author to Book.

2

Create an inline admin class for Author

In the Django admin file, import admin and create a class called AuthorInline that inherits from admin.TabularInline. Set its model attribute to Author.

Django

from django.db import models

class Book(models.Model):
    title = models.CharField(max_length=100)

class Author(models.Model):
    name = models.CharField(max_length=50)
    book = models.ForeignKey(Book, on_delete=models.CASCADE)

# Your code here

Hint

Use admin.TabularInline to create a simple inline table for authors.

3

Create a BookAdmin class with AuthorInline

Create a Django admin class called BookAdmin that inherits from admin.ModelAdmin. Add an attribute inlines and set it to a list containing AuthorInline.

Django

from django.db import models
from django.contrib import admin

class Book(models.Model):
    title = models.CharField(max_length=100)

class Author(models.Model):
    name = models.CharField(max_length=50)
    book = models.ForeignKey(Book, on_delete=models.CASCADE)

class AuthorInline(admin.TabularInline):
    model = Author

# Create BookAdmin with inlines
# Your code here

Hint

Set inlines to a list with your inline class inside.

4

Register Book model with BookAdmin

Register the Book model with the Django admin site using admin.site.register(Book, BookAdmin).

Django

from django.db import models
from django.contrib import admin

class Book(models.Model):
    title = models.CharField(max_length=100)

class Author(models.Model):
    name = models.CharField(max_length=50)
    book = models.ForeignKey(Book, on_delete=models.CASCADE)

class AuthorInline(admin.TabularInline):
    model = Author

class BookAdmin(admin.ModelAdmin):
    inlines = [AuthorInline]

# Register Book with BookAdmin
# Your code here

Hint

Use admin.site.register to connect your model and admin class.

Practice

1. What is the main purpose of using inline models in Django admin?

easy

A. To edit related models together on the same admin page

B. To create new database tables automatically

C. To improve website loading speed

D. To add custom CSS styles to admin pages

Solution

1. Step 1: Understand inline models concept

   Inline models allow editing related data on the same admin page, making management easier.

2. Step 2: Identify the main purpose

   The main goal is to edit related models together, not to create tables or change styles.

3. Final Answer:

   To edit related models together on the same admin page -> Option A

4. Quick Check:

   Inline models = edit related data together [OK]

Hint: Inline means editing related data on one page [OK]

Common Mistakes:

• Thinking inline models create new tables
• Confusing inline models with styling options
• Assuming inline models improve site speed

2. Which Django admin class is used to display related models in a table format inline?

easy

A. StackedInline

B. InlineModelAdmin

C. TabularInline

D. RelatedInline

Solution

1. Step 1: Recall inline classes in Django admin

   Django provides two main inline classes: TabularInline and StackedInline.

2. Step 2: Match class to table format

   TabularInline shows related models in a compact table, while StackedInline shows stacked blocks.

3. Final Answer:

   TabularInline -> Option C

4. Quick Check:

   Table format inline = TabularInline [OK]

Hint: Tabular means table layout, Stacked means block layout [OK]

Common Mistakes:

• Choosing StackedInline for table layout
• Using non-existent classes like InlineModelAdmin
• Confusing RelatedInline with official classes

3. Given this Django admin code snippet, what will be the result when editing a Book in admin?

class ChapterInline(admin.TabularInline):
    model = Chapter

class BookAdmin(admin.ModelAdmin):
    inlines = [ChapterInline]

admin.site.register(Book, BookAdmin)

medium

A. Chapters will not appear in the Book admin page

B. Books will be listed in a table inside Chapter admin

C. An error will occur because inlines must be StackedInline

D. Chapters related to the Book will be editable inline in a table format

Solution

1. Step 1: Understand the inline setup

   The ChapterInline uses TabularInline with model Chapter, linked to BookAdmin inlines.

2. Step 2: Predict admin behavior

   When editing a Book, its related Chapters appear inline in a table for editing.

3. Final Answer:

   Chapters related to the Book will be editable inline in a table format -> Option D

4. Quick Check:

   TabularInline in BookAdmin = Chapters editable inline [OK]

Hint: Inlines in ModelAdmin show related models on that model's page [OK]

Common Mistakes:

• Thinking Chapters appear inside Chapter admin
• Assuming no inline display without StackedInline
• Confusing which model is inline of which

4. Identify the error in this Django admin inline setup:

class AuthorInline(admin.TabularInline):
    model = Author

class BookAdmin(admin.ModelAdmin):
    inlines = [AuthorInline]

admin.site.register(Book, BookAdmin)

medium

A. Author model cannot be inline of Book because no ForeignKey to Book exists

B. TabularInline must be replaced with StackedInline

C. The inlines list must be a tuple, not a list

D. admin.site.register should register Author, not Book

Solution

1. Step 1: Check model relationships

   For inline to work, the inline model (Author) must have a ForeignKey to the parent model (Book).

2. Step 2: Identify missing ForeignKey

   Author likely does not have a ForeignKey to Book, so it cannot be inline in BookAdmin.

3. Final Answer:

   Author model cannot be inline of Book because no ForeignKey to Book exists -> Option A

4. Quick Check:

   Inline model needs ForeignKey to parent [OK]

Hint: Inline model must have ForeignKey to parent model [OK]

Common Mistakes:

• Thinking TabularInline vs StackedInline causes error
• Believing inlines must be tuples, not lists
• Registering wrong model in admin.site.register

5. You want to allow editing multiple related Comment objects inside a Post admin page. Comments have a ForeignKey to Post. Which is the best way to set this up for easy editing and better user experience?

hard

A. Register Comment model separately without inlines

B. Create a CommentInline class using TabularInline and add it to PostAdmin inlines

C. Use StackedInline for CommentInline but do not add it to PostAdmin

D. Add a ForeignKey from Post to Comment and use TabularInline in CommentAdmin

Solution

1. Step 1: Use ForeignKey direction correctly

   Comments have ForeignKey to Post, so Comment can be inline in PostAdmin.

2. Step 2: Choose inline class and add to PostAdmin

   TabularInline is good for multiple related objects; adding CommentInline to PostAdmin inlines enables editing comments inside Post.

3. Final Answer:

   Create a CommentInline class using TabularInline and add it to PostAdmin inlines -> Option B

4. Quick Check:

   ForeignKey from Comment to Post + TabularInline in PostAdmin = best UX [OK]

Hint: Inline related model with ForeignKey to parent for easy editing [OK]

Common Mistakes:

• Not adding inline to parent admin class
• Using wrong ForeignKey direction
• Registering models separately without inlines