Small update: Wrapping the view function with *@transaction.atomic* fixes the issue -- the queries execute in a transaction as expected.
So I guess my immediate problem is resolved. If anyone has an idea, I'd still love to know why the view is ignoring the top-level TRANSACTION_ATOMIC setting. In case it's happening elsewhere that I'm not aware of. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/984cd123-8d50-4c08-ad65-94b7a0a43fd4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
