DeleteView for removal in Django - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the generic DeleteView class from Django.

Django

from django.views.generic import [1]

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

ACreateView

BListView

CDeleteView

DUpdateView

Attempts:

3 left

💡 Hint

Common Mistakes

Importing ListView instead of DeleteView

Using CreateView or UpdateView which are for other purposes

The DeleteView is the generic view used to delete objects in Django.

2fill in blank

medium

Complete the code to specify the model to delete in a DeleteView subclass.

Django

class BookDeleteView(DeleteView):
    model = [1]

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

AReview

BAuthor

CPublisher

DBook

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different model name than the view's purpose

Forgetting to set the model attribute

The model attribute tells the DeleteView which model to delete. Here, it should be Book.

3fill in blank

hard

Fix the error in the DeleteView by completing the code to redirect after deletion.

Django

class BookDeleteView(DeleteView):
    model = Book
    success_url = [1]

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

A'/books/'

Breverse('book-list')

Credirect('book-list')

Drender('book-list.html')

Attempts:

3 left

💡 Hint

Common Mistakes

Using reverse() directly without lazy evaluation

Using redirect() or render() which are not valid here

The success_url must be a URL string or a lazy URL. Here, a string URL like '/books/' is correct.

4fill in blank

hard

Fill both blanks to complete the URL pattern for the DeleteView.

Django

path('[1]/<int:pk>/delete/', [2].as_view(), name='book-delete')

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

Abooks

BBookDeleteView

Cbook

DBookListView

Attempts:

3 left

💡 Hint

Common Mistakes

Using plural 'books' in URL when singular is expected

Using wrong view class like BookListView

The URL pattern uses 'book' as the prefix and the view class is BookDeleteView.

5fill in blank

hard

Fill all three blanks to complete the DeleteView with template name and success URL.

Django

class BookDeleteView(DeleteView):
    model = [1]
    template_name = '[2]'
    success_url = '[3]'

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

ABook

Bbooks/book_confirm_delete.html

C/books/

DAuthor

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong model name

Incorrect template path

Wrong success URL path

The model is Book, the template is the confirm delete page for books, and the success URL redirects to the books list.

Practice

1. What is the main purpose of Django's DeleteView?

easy

A. To list all objects of a model

B. To create a new object in the database

C. To display a confirmation page and delete an object upon confirmation

D. To update an existing object in the database

Solution

1. Step 1: Understand DeleteView functionality

   DeleteView is designed to handle deletion of objects with a confirmation step.

2. Step 2: Compare with other views

   Creating, updating, and listing objects are handled by other views like CreateView, UpdateView, and ListView.

3. Final Answer:

   To display a confirmation page and delete an object upon confirmation -> Option C

4. Quick Check:

   DeleteView = confirmation + delete [OK]

Hint: DeleteView always confirms before deleting [OK]

Common Mistakes:

• Confusing DeleteView with CreateView or UpdateView
• Thinking DeleteView deletes without confirmation
• Assuming DeleteView lists objects

2. Which of the following is the correct way to specify the URL to redirect after a successful delete in a DeleteView?

easy

A. redirect_url = reverse('home')

B. success_redirect = 'home/'

C. url_redirect = 'home/'

D. success_url = reverse_lazy('home')

Solution

1. Step 1: Identify correct attribute for redirect

   DeleteView uses success_url to define where to go after deletion.

2. Step 2: Use reverse_lazy for URL resolution

   Since URLs are resolved lazily in class-based views, reverse_lazy is preferred over reverse.

3. Final Answer:

   success_url = reverse_lazy('home') -> Option D

4. Quick Check:

   success_url + reverse_lazy = correct redirect [OK]

Hint: Use success_url with reverse_lazy for redirects [OK]

Common Mistakes:

• Using reverse instead of reverse_lazy in class attributes
• Using wrong attribute names like redirect_url
• Assigning plain strings without URL reversing

3. Given this DeleteView code snippet, what happens when the user confirms deletion?

class BookDeleteView(DeleteView):
    model = Book
    template_name = 'books/book_confirm_delete.html'
    success_url = reverse_lazy('book-list')

medium

A. The book is deleted and user is redirected to the book list page

B. The book is updated and user stays on the same page

C. The book is deleted but user stays on the confirmation page

D. Nothing happens because success_url is incorrect

Solution

1. Step 1: Confirm DeleteView behavior on confirmation

   When the user confirms, the object specified by model is deleted.

2. Step 2: Check success_url usage

   After deletion, the user is redirected to the URL given by success_url, here 'book-list'.

3. Final Answer:

   The book is deleted and user is redirected to the book list page -> Option A

4. Quick Check:

   Delete + redirect = The book is deleted and user is redirected to the book list page [OK]

Hint: Confirm deletes object and redirects to success_url [OK]

Common Mistakes:

• Thinking the object is updated instead of deleted
• Assuming user stays on confirmation page after delete
• Believing success_url must be a string, not reverse_lazy

4. Identify the error in this DeleteView subclass:

class ArticleDeleteView(DeleteView):
    model = Article
    template_name = 'articles/delete.html'
    success_url = reverse('article-list')

medium

A. template_name should be 'article_confirm_delete.html'

B. Using reverse() instead of reverse_lazy() for success_url

C. Missing the get_object() method override

D. model attribute should be a string, not a class

Solution

1. Step 1: Check success_url assignment in class attribute

   Class attributes are evaluated at import time, so reverse() causes errors here.

2. Step 2: Use reverse_lazy() for lazy URL resolution

   reverse_lazy() delays evaluation until runtime, fixing the error.

3. Final Answer:

   Using reverse() instead of reverse_lazy() for success_url -> Option B

4. Quick Check:

   reverse_lazy needed for class attributes [OK]

Hint: Use reverse_lazy in class attributes, not reverse [OK]

Common Mistakes:

• Overriding get_object() unnecessarily
• Assuming template_name must follow a strict name
• Using model as string instead of class (both work but class preferred)

5. You want to customize the confirmation page of a DeleteView to show extra context data like the current user's name. Which method should you override to add this data?

hard

A. get_context_data()

B. get_object()

C. form_valid()

D. dispatch()

Solution

1. Step 1: Understand where to add extra template data

   Extra data for templates is added by overriding get_context_data().

2. Step 2: Confirm other methods' purposes

   get_object() fetches the object, form_valid() handles form submission, and dispatch() manages request flow.

3. Final Answer:

   get_context_data() -> Option A

4. Quick Check:

   Extra template data = get_context_data() [OK]

Hint: Add extra template info by overriding get_context_data() [OK]

Common Mistakes:

• Overriding form_valid() to add context data
• Changing get_object() to add template variables
• Using dispatch() for template context