Inline models for related data in Django - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the inline admin class.

Django

from django.contrib import admin
from .models import Book, Chapter

class ChapterInline([1]):
    model = Chapter

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

Aadmin.StackedInline

Badmin.ModelAdmin

Cadmin.TabularInline

Dadmin.InlineModelAdmin

Attempts:

3 left

💡 Hint

Common Mistakes

Using ModelAdmin instead of an inline class.

Confusing TabularInline with StackedInline.

The StackedInline class is used to display related models inline in a stacked layout.

2fill in blank

medium

Complete the code to register the Book model with the Chapter inline.

Django

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

admin.site.register(Book, BookAdmin)

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

AChapterInline[]

BChapterInline()

C[ChapterInline]

DChapterInline

Attempts:

3 left

💡 Hint

Common Mistakes

Using parentheses to create an instance.

Not wrapping the inline class in a list.

The inlines attribute expects a list of inline classes, not instances. So just the class name without parentheses is correct.

3fill in blank

hard

Fix the error in the inline admin by completing the missing attribute.

Django

class ChapterInline(admin.StackedInline):
    model = Chapter
    extra = [1]

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

A2

B'2'

CTrue

DFalse

Attempts:

3 left

💡 Hint

Common Mistakes

Using quotes around the number.

Using boolean values instead of an integer.

The extra attribute expects an integer indicating how many extra blank forms to show. It should not be a string.

4fill in blank

hard

Fill both blanks to customize the inline admin to show 3 extra forms and use a tabular layout.

Django

class ChapterInline(admin.[1]):
    model = Chapter
    extra = [2]

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

ATabularInline

BStackedInline

C3

D1

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing StackedInline with tabular layout.

Setting extra to 1 instead of 3.

Using TabularInline shows related objects in a table. Setting extra = 3 shows three blank forms for new related objects.

5fill in blank

hard

Fill all three blanks to create an inline admin for a related model Author with 2 extra stacked forms and register it with the Book model.

Django

class [1](admin.[2]):
    model = Author
    extra = [3]

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

admin.site.register(Book, BookAdmin)

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

AAuthorInline

BStackedInline

C2

DTabularInline

Attempts:

3 left

💡 Hint

Common Mistakes

Using TabularInline instead of StackedInline.

Forgetting to name the class properly.

Setting extra to wrong number.

The inline admin class is named AuthorInline, uses StackedInline for layout, and sets extra = 2 to show two blank forms.

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