#2227: atch] transaction.commit()/rollback() should be aware of nested calls to
transaction.managed(True)
---------------------------------------------------+------------------------
Reporter: md...@yandex.ru | Owner: nobody
Status: assigned | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords:
transaction, nest, scope, nested, rollback, commit
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
---------------------------------------------------+------------------------
Changes (by jacmkno):
* keywords: transaction, nest, scope => transaction, nest, scope,
nested, rollback, commit
Comment:
I really like Glenn's approach because the lack of nested transaction
management in the back-end databases is made transparent to the
programmer. I think that solving this problem with database features will
be a good idea when when those features are ready to fully support nested
transactions. In the current implementation good documentation of
transactional functions in your app is required to mantain data
consitency, and Glen's approach would reduce this need significantly.
--
Ticket URL: <http://code.djangoproject.com/ticket/2227#comment:23>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
