2010/5/17 Ian Lewis <ianmle...@gmail.com>: > > I suppose that it's worth mentioning that any support for nested > transactions will not be portable to different databases (particularly > MySQL) and probably would need to be documented accordingly.
How do you mean? Django-level transaction block nesting is portable to any database that supports transactions: The top-level transaction subsumes nested transactional blocks. If you are referring to SQL savepoints, supporting them is entirely optional: nested transaction blocks do not depend on it in any way. Savepoints are more like an optional performance optimization than anything else, and just give applications the option of doing finer-grained failure recovery in certain cases without changing the meaning of transactional blocks. (The proposal above only mentions savepoints for completeness, and because support for them would be natural to integrate.) -- 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.
