Django 1.6 中的 ATOMIC_REQUEST 和事务

素材狗 2022-01-01 20:45:59 文章分类：Python问题点击数：次

文章标签

ATOMIC_REQUEST and Transactions in Django 1.6(Django 1.6 中的 ATOMIC_REQUEST 和事务)

本文介绍了Django 1.6 中的 ATOMIC_REQUEST 和事务的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！

问题描述

给定以下代码:

from django.db import transaction

@transaction.atomic
def viewfunc(request):
    # This code executes inside a transaction.
    do_stuff()

根据我对 Django 1.6 中事务的理解，如果 do_stuff 抛出异常，比如 IntegrityError，那么事务将正确回滚.但是由于 Django 本身正在调用视图，没有什么可以阻止 IntegrityError 从调用堆栈上升并导致 HTTP 500 错误是吗?让我们假设这不是我们想要的，因为我们想要优雅地处理错误，但仍然获得回滚功能.

From my understanding of transactions in Django 1.6 if do_stuff throws an exception, say an IntegrityError, then the transaction will be rolled back right. But since Django itself is calling the view nothing will stop the IntegrityError from rising up the call stack and causing an HTTP 500 error yes? Let's assume that's not what we want, as we want to gracefully handle the error, but still get the rollback functionality.

所以我想明显的想法是好的，不要那样做，使用 transaction.atomic 作为上下文管理器，它被包装在一个 try except 块中，就像这里的例子:

So I guess the obvious thought is well, don't do that, use transaction.atomic as a context manager that is wrapped in a try except block like the example here:

try:
    with transaction.atomic():
        generate_relationships()
except IntegrityError:
    handle_exception()

好的.但是，如果您想通过在 db 配置中设置 ATOMIC_REQUEST = True 来使用每个 HTTP 请求的事务功能，这意味着 django 实际上只会将 transaction.atomic 装饰添加到您的视图中，这不会t 捕获任何异常.ATOMIC_REQUEST 有什么用?您为什么要让数据库错误一直传播到用户?

Fine. But then if you want to use the Transaction per HTTP Request functionality by setting ATOMIC_REQUEST = True in your db config, which means django will in effect just add the transaction.atomic decorate to your view, which won't catch any exceptions. How is ATOMIC_REQUEST even useful? Why would you ever want to let your Database errors propagate all the way up to the user?

所以我的问题是.

我在这里遗漏了什么或者我的理解是否正确?
如果我是对的，使用 ATOMIC_REQUEST 的用例是什么?我应该编写 urls.hadler500 还是应该实现一些中间件来捕获错误?

What am I missing here or is my understanding correct?
If I'm correct what is a use case for using ATOMIC_REQUEST? Am I expected to write a urls.hadler500 or should I implement some middleware to catch the errors?