Delete multiple objects in django

Detailed walkthrough for deletion

In more complex situations, you may want to delete objects by more than just IDs, or need to manage deletion as part of a wider operation. 👀

# Deletes instances where a field satisfies a condition. We only keep the fresh ones!
MyModel.objects.filter(created_at__lte=some_date).delete()


Remember: .delete() doesn't call .save() or trigger pre_delete or post_delete signals. It's a silent killer. 🕵️

Using ModelForm and views for deletion

Crafting the destruction form with ModelForm

When delete confirmations are required in your workflow, Django’s ModelForm to the rescue:

from django import forms
from django.shortcuts import redirect

class DeleteObjectForm(forms.ModelForm):
    class Meta:
        model = MyModel
        fields = []

def delete_objects(request):
    if request.method == 'POST':
        form = DeleteObjectForm(request.POST)
        if form.is_valid():
            form.instance.delete()  # 1 Click, 1 Kill!
            return redirect('object-list')
    else:
        form = DeleteObjectForm()
    return render(request, 'delete_confirm.html', {'form': form})


User confirmation ensures safer deletion while providing a more intuitive interface. 🛡️

Handling form submissions in views

In your views, handle form submissions for deletion while implementing Django's CSRF protection:

from django.views.decorators.csrf import csrf_protect

@csrf_protect
def delete_multiple(request):
    if request.method == 'POST':
        object_ids = request.POST.getlist('object_ids')
        MyModel.objects.filter(id__in=object_ids).delete()  # Mass extermination begins here
        return redirect('object-list')


This view works well with a form containing checkboxes or multiple select options, empowering users to choose which objects to obliterate.

Advanced deletion practices

Unleashing the power of third-party packages

For more complex filtering, 3rd party packages like django-filter expand your django-ninja toolkit:

import django_filters

class MyModelFilter(django_filters.FilterSet):
    class Meta:
        model = MyModel
        fields = ['field_name']

# In your view
my_filter = MyModelFilter(request.GET, queryset=MyModel.objects.all())
my_filter.qs.delete()  # Filters + Deletion = Power combo


Employing Django's generic views

Django’s built-in generic views streamline the deletion process. Let the DeleteView do the heavy lifting:

from django.views.generic.edit import DeleteView
from django.urls import reverse_lazy

class MyModelDelete(DeleteView):
    model = MyModel
    success_url = reverse_lazy('object-list')  # See you on the other side!

# urls.py
path('delete/<int:pk>/', MyModelDelete.as_view(), name='mymodel_delete')


Optimising user experience and security

Building a firefighting user interface

Display objects on the webpage with a deletion button each. Users like control and simplicity:

<!-- Your template file -->
<form method="POST">{% csrf_token %}
  <!-- Loop through objects -->
  {% for object in object_list %}
    <div>
      <span>{{ object.name }}</span>
      <!-- Delete button -->
      <button type="submit" name="object_id" value="{{ object.id }}">Send him away!</button>
    </div>
  {% endfor %}
</form>


Shielding against CSRF

Don’t forget {% csrf_token %} for securing your form submissions against CSRF attacks. Remember, prevention is better than cure!

Ensuring safe journey via POST

Always use POST requests for deletion to protect against accidental data removals. Like storing dynamite in a safe box:

<form method="POST" action="{% url 'delete_multiple' %}">
  {% for object in object_list %}
    <input type="checkbox" name="object_ids" value="{{ object.id }}">{{ object.name }}
  {% endfor %}
  <button type="submit">Delete Selected</button>  <!-- Choose who won't be seeing tomorrow -->
</form>
