Snippet

Django atomic Transaction Management

The atomic context manager wraps database operations in a transaction, ensuring all changes commit together or none commit if an error occurs. This prevents partial updates that would corrupt data integrity. Using update_fields limits the SQL UPDATE to only changed columns, improving performance. The transaction automatically rolls back when an exception propagates outside the with block.

snippet.py

python

from django.db import transaction
from decimal import Decimal
 
def transfer_funds(sender, receiver, amount):
    with transaction.atomic():
        sender.balance -= amount
        sender.save(update_fields=['balance'])
 
        receiver.balance += amount
        receiver.save(update_fields=['balance'])
 
        TransactionLog.objects.create(
            from_account=sender,
            to_account=receiver,
            amount=amount
        )
 
        if sender.balance < 0:
            raise ValueError('Insufficient funds')
 
def batch_import_products(products_data):
    try:
        with transaction.atomic():
            for data in products_data:
                Product.objects.create(**data)
            return True
    except Exception:
        return False

django

Breakdown

with transaction.atomic():

Creates a transaction block; all operations succeed or all fail together

sender.save(update_fields=['balance'])

Partial update only the balance field, avoiding timestamp changes

raise ValueError('Insufficient funds')

Uncaught exception causes automatic rollback of all changes

except Exception:

Catches rollback exception; data remains consistent

Previous snippet Next snippet

More Intermediate Python exercises →

Django atomic Transaction Management

Related