Upgrading to Django 1.6 introduced a complex problem in my code: database operations that are triggered by a signal post_savefall into with transaction.atomic(): the Django block get_or_create().
post_save
with transaction.atomic():
get_or_create()
The impact on me is that custom sql (unmanaged) does not get db bindings in time.
Is there any other signal that I can use that is sent after it obj.save()leaves its atomic block?
obj.save()
Or am I diagnosed wrong?
Django get_or_create() save() , , post_save, .
save()
get_or_create() transaction.atomic().
transaction.atomic()
, .