db.transaction.non_atomic_requests()

non_atomic_requests(using=None) [source]

This decorator will negate the effect of ATOMIC_REQUESTS for a given view:

from django.db import transaction

@transaction.non_atomic_requests
def my_view(request):
    do_stuff()

@transaction.non_atomic_requests(using='other')
def my_other_view(request):
    do_stuff_on_the_other_database()

It only works if it’s applied to the view itself.

Links:

https://docs.djangoproject.com/en/1.10/topics/db/transactions/#django.db.transaction.non_atomic_requests

doc_Django

2016-10-09 18:36:27

Comments

Popular Articles

db.transaction.atomic() atomic(using=None, savepoint=True) [source] Atomicity is the defining property of database transactions. atomic allows us to create a block of cod

db_transaction db_transaction($name = NULL, array $options = array()) Returns a new transaction object for the active database. Parameters string $name: Optional n

db\Transaction $db $db public property The database connection that this transaction is associated with. public yii\db\Connection $db = null

db.transaction.rollback() rollback(using=None) [source] These functions take a using argument which should be the name of a database. If it isn’t provided, Django uses the

db\Transaction rollBack() rollBack() public method Rolls back a transaction. public void rollBack ( )throws yii\db\Exception if the transaction is not active