Not nesting version of @atomic() in Django? : <p>From the <a href="https://docs.djangoproject.com/en/dev/topics/db/transactions/#django.db.transaction.atomic">docs of atomic()</a></p>

<blockquote>
  <p>atomic blocks can be nested</p>
</blockquote>

<p>This sound like a great feature, but in my use case I want the opposite: I want the transaction to be durable as soon as the block decorated with <code>@atomic()</code> gets left successfully.</p>

<p>Is there a way to ensure durability in django's transaction handling?</p>

<h1>Background</h1>

<p>Transaction are ACID. The "D" stands for durability. That's why I think transactions can't be nested without loosing feature "D".</p>

<p>Example: If the inner transaction is successful, but the outer transaction is not, then the outer and the inner transaction get rolled back. The result: The inner transaction was not durable.</p>

<p>I use PostgreSQL, but AFAIK this should not matter much.</p>
