Nested commit_on_success

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
def nested_commit_on_success(func):
    """Like commit_on_success, but doesn't commit existing transactions.

    This decorator is used to run a function within the scope of a 
    database transaction, committing the transaction on success and
    rolling it back if an exception occurs.

    Unlike the standard transaction.commit_on_success decorator, this
    version first checks whether a transaction is already active.  If so
    then it doesn't perform any commits or rollbacks, leaving that up to
    whoever is managing the active transaction.
    """
    commit_on_success = transaction.commit_on_success(func)
    def _nested_commit_on_success(*args, **kwds):
        if transaction.is_managed():
            return func(*args,**kwds)
        else:
            return commit_on_success(*args,**kwds)
    return transaction.wraps(func)(_nested_commit_on_success)

More like this

  1. PositionField by jpwatts 5 years, 9 months ago
  2. Model Hooks by jakecr 4 years, 3 months ago
  3. django_bulk_save.py - defer saving of django models to bulk SQL commits by preetkukreti 4 years, 2 months ago
  4. Memento by manelvf 3 years, 3 months ago
  5. RandomObjectManager by jjdelc 3 years, 1 month ago

Comments

demichej (on August 10, 2011):

Thanks, RFK! I love it! I wonder why Django doesn't just use this decorator instead of its normal commit_on_success() what am I missing? It seems like this works exactly like commit_on_success, except it won't open a new transaction if one is already being managed?

#

demanzano (on August 11, 2011):

Very useful!

just a question, this code is for a decorator (the '@' operator) but what if I would use the 'with' operator ? How should I modify this code to be run with 'with' ? Thanks anyway !

#

(Forgotten your password?)