#9964: Transaction middleware closes the transaction only when it's marked as
dirty
---------------------------------------------------+------------------------
Reporter: ishirav | Owner:
mtredinnick
Status: assigned | Milestone: 1.3
Component: Database layer (models, ORM) | Version: 1.0-beta-1
Resolution: | Keywords:
transactions
Stage: Accepted | Has_patch: 1
Needs_docs: 1 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by shai):
Jeez, people. What's required here is a design decision by core
committers, which I called for [comment:21 more than 7 months ago]:
>
> Since transactions are deep, and changing their behavior might break
user applications, I suggested (...) a three-step path towards correct
behavior (...) If you'd consider a patch which just always closes
transactions, just say so, and I'll provide one.
>
The expressions of disbelief and ridicule, accompanied by repetition of
obviously correct statements about the right way to manage transactions,
are not helpful.
--
Ticket URL: <http://code.djangoproject.com/ticket/9964#comment:37>
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.
