> Yes: we're talking about Django's transaction management layer (that is, the > code in django.db.transaction), which controls how Python-level transaction > blocks map to SQL transactions. > > The original email and writeup has a full explanation. :) >
Yes. What I was getting at is that django's transaction management layer is a layer over top of the database's own transaction management not a full transaction layer implemented at the application level. In any case the underlying database doesn't support nested transactions in the case of MySQL. Starting a transaction within a transaction does not subsume the current transaction. It does an implicit commit, ending the current transaction and starts a new top level transaction. In any case it's probably not worth talking much more about it since you can probably implement the functionality using savepoints at least with InnoDB. But I did want to bring up that there are database portability implications here. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
