Django Academy · 课时

DeleteView 与 success_url

确认删除并在之后重定向

DeleteView 与 success_url 是 CoddyKit 上的免费 Django Academy 课时。这是第 3 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Django Academy 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Django Academy 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Removing Records Safely

Sometimes data has to go. DeleteView handles removing a record, with a confirmation step built in. 🗑️

Meet DeleteView

DeleteView loads one object by its pk and prepares to delete it once the user confirms.

from django.views.generic import DeleteView

class PostDelete(DeleteView):
    model = Post

Why Confirmation Matters

Deleting is permanent, so DeleteView shows a confirmation page on GET before anything is removed.

The Confirm Template

By default DeleteView looks for app/model_confirm_delete.html, like post_confirm_delete.html.

The Confirmation Form

The confirm page posts back to the same URL, and that POST request is what actually triggers the delete.

<form method="post">{% csrf_token %}
  <p>Delete {{ object }}?</p>
  <button>Yes, delete</button>
</form>

Where success_url Comes In

After deleting, the user needs somewhere to go. success_url sets that destination explicitly.

from django.urls import reverse_lazy

class PostDelete(DeleteView):
    model = Post
    success_url = reverse_lazy("post_list")

Why reverse_lazy Here

Use reverse_lazy, not reverse, because URLs are not ready when the class body is first read at import time.

reverse vs reverse_lazy

reverse resolves a URL immediately, while reverse_lazy waits until the value is actually needed.

Wiring the Delete URL

The delete URL captures a pk so DeleteView knows which record to remove.

path("<int:pk>/delete/", PostDelete.as_view()),

Linking to Delete

From a detail page, link to delete using the url tag and the object pk so the right record is targeted.

<a href="{% url 'post_delete' object.pk %}">Delete</a>

Safe by Design

The GET confirm plus POST delete pattern means no record vanishes from a stray click or a crawler. ✅

Quick Check

What does success_url control in a DeleteView?

Recap: Deleting Records

You used DeleteView with a GET confirm and POST delete, then sent users onward with success_url and reverse_lazy. 🎉

常见问题解答

「DeleteView 与 success_url」课时是免费的吗？

是的 — 「DeleteView 与 success_url」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Django Academy 课程的其余内容，请升级到 CoddyKit PRO。 Django Academy 课程共包含 4 节课。

「DeleteView 与 success_url」这节课中我会学到什么？

确认删除并在之后重定向你通过在浏览器中直接运行的动手代码来练习 Django Academy，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Django Academy 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Django Academy 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 3 节课，共 4 节。

「DeleteView 与 success_url」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Django Academy 课中编写并运行代码吗？

能。每节 Django Academy 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Django Academy