--- title: Django Async ORM: How to Handle Database Transactions in... description: Wrapping transaction.atomic() around awaited ORM calls in a Django async view does not give reliable transaction management in versions without direct async... canonical: https://daily.dev/posts/django-async-orm-how-to-handle-database-transactions-in-async-views-q51wkylvs twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Django Async ORM: How to Handle Database Transactions in Async Views | daily.dev og:description: Wrapping transaction.atomic() around awaited ORM calls in a Django async view does not give reliable transaction management in versions without direct async... og:url: https://daily.dev/posts/django-async-orm-how-to-handle-database-transactions-in-async-views-q51wkylvs og:image: https://api.daily.dev/og/posts/q51wKyLvS.png og:image:alt: Django Async ORM: How to Handle Database Transactions in Async Views og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Django Async ORM: How to Handle Database Transactions in Async Views **[C\# Corner](https://daily.dev/sources/csharpcorner)** · 11 min read · 0 upvotes · 0 comments ## Summary Wrapping transaction.atomic() around awaited ORM calls in a Django async view does not give reliable transaction management in versions without direct async transaction support. The fix: move the whole transactional operation into a synchronous function and call it from the async view with sync_to_async(), using thread_sensitive=True. A money-transfer example shows select_for_update() for row locks and sorted account IDs to reduce deadlock risk. ATOMIC_REQUESTS should not be assumed to cover async views in those versions. Keep transactions short and use transaction.on_commit() for simple post-commit side effects. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why doesn't transaction.atomic() work correctly inside a Django async view? The transaction context does not become asynchronous just because the surrounding function uses async def; transaction.atomic() is a synchronous transaction-management API. In Django versions where async transactions aren't supported, wrapping awaited ORM calls in transaction.atomic() inside an async view is not a safe way to group those operations. _Developers debugging Django async transaction bugs can find patterns like this one on daily.dev._ ### How do I safely run a database transaction from a Django async view? Move the entire transactional operation into a synchronous function that uses transaction.atomic(), then call that function from the async view with sync_to_async(), passing thread_sensitive=True. The transaction begins and ends inside the synchronous function, with no await expression placed inside the transaction block. _daily.dev surfaces practical fixes like this for developers building async Django services._ ### How can I reduce deadlocks when locking multiple rows in a Django transaction with select_for_update()? Sort the account or record IDs before retrieving rows with select_for_update(), so concurrent transactions acquire locks in a consistent order. This reduces deadlock risk when concurrent transfers involve the same accounts, though it does not eliminate every possible deadlock scenario. _Teams hardening concurrent database code can track techniques like this via daily.dev._ ## Similar posts on daily.dev - [How to Prevent Race Conditions in Django](https://daily.dev/posts/how-to-prevent-race-conditions-in-django-mrablcwec) · freeCodeCamp · 0 upvotes · 0 comments - [Building async Python applications with Tortoise ORM and Amazon Aurora DSQL](https://daily.dev/posts/building-async-python-applications-with-tortoise-orm-and-amazon-aurora-dsql-mfleo5e03) · AWS Database Blog · 0 upvotes · 0 comments - [SQLAlchemy 2 In Practice - Chapter 7: Asynchronous SQLAlchemy](https://daily.dev/posts/sqlalchemy-2-in-practice---chapter-7-asynchronous-sqlalchemy-rwgj7jxq3) · Miguel Grinberg · 0 upvotes · 0 comments - [A stray commit buried multiple levels deep cost me months](https://daily.dev/posts/a-stray-commit-buried-multiple-levels-deep-cost-me-months-auv5pc3lh) · Hacker News · 0 upvotes · 1 comments - [SQL: Incorrect by Construction](https://daily.dev/posts/sql-incorrect-by-construction-qbpedkdak) · Lobsters · 3 upvotes · 0 comments --- Tags: [#python](https://daily.dev/tags/python), [#django](https://daily.dev/tags/django) [View this post on daily.dev](https://daily.dev/posts/django-async-orm-how-to-handle-database-transactions-in-async-views-q51wkylvs) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Django Async ORM: How to Handle Database Transactions in Async Views","url":"https://daily.dev/posts/django-async-orm-how-to-handle-database-transactions-in-async-views-q51wkylvs","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/django-async-orm-how-to-handle-database-transactions-in-async-views-q51wkylvs"},"datePublished":"2026-10-29T14:12:21.757Z","dateModified":"2026-10-29T14:16:09.258Z","description":"Wrapping transaction.atomic() around awaited ORM calls in a Django async view does not give reliable transaction management in versions without direct async...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/713dc50994292fd88fead1ee36476b0b?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/713dc50994292fd88fead1ee36476b0b?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"C# Corner","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"C# Corner","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/ada2d584df6241748fc4e71878dc70a3","url":"https://daily.dev/sources/csharpcorner"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/django-async-orm-how-to-handle-database-transactions-in-async-views-q51wkylvs","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"python,django","timeRequired":"PT11M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"C# Corner","item":"https://daily.dev/sources/csharpcorner"},{"@type":"ListItem","position":3,"name":"Django Async ORM: How to Handle Database Transactions in Async Views"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/django-async-orm-how-to-handle-database-transactions-in-async-views-q51wkylvs#faq","mainEntity":[{"@type":"Question","name":"Why doesn't transaction.atomic() work correctly inside a Django async view?","acceptedAnswer":{"@type":"Answer","text":"The transaction context does not become asynchronous just because the surrounding function uses async def; transaction.atomic() is a synchronous transaction-management API. In Django versions where async transactions aren't supported, wrapping awaited ORM calls in transaction.atomic() inside an async view is not a safe way to group those operations. Developers debugging Django async transaction bugs can find patterns like this one on daily.dev."}},{"@type":"Question","name":"How do I safely run a database transaction from a Django async view?","acceptedAnswer":{"@type":"Answer","text":"Move the entire transactional operation into a synchronous function that uses transaction.atomic(), then call that function from the async view with sync_to_async(), passing thread_sensitive=True. The transaction begins and ends inside the synchronous function, with no await expression placed inside the transaction block. daily.dev surfaces practical fixes like this for developers building async Django services."}},{"@type":"Question","name":"How can I reduce deadlocks when locking multiple rows in a Django transaction with select_for_update()?","acceptedAnswer":{"@type":"Answer","text":"Sort the account or record IDs before retrieving rows with select_for_update(), so concurrent transactions acquire locks in a consistent order. This reduces deadlock risk when concurrent transfers involve the same accounts, though it does not eliminate every possible deadlock scenario. Teams hardening concurrent database code can track techniques like this via daily.dev."}}]} ```