#9964: Transaction middleware closes the transaction only when it's marked as
dirty
---------------------------------------------------+------------------------
Reporter: ishirav | Owner:
mtredinnick
Status: assigned | Milestone: 1.2
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 |
---------------------------------------------------+------------------------
Changes (by russellm):
* milestone: 1.1 => 1.2
Comment:
After discussing with Jacob and Malcolm, we've decided to defer this one
from v1.1.
From a purely code perspective, the patches on this ticket aren't ready
for trunk. In particular, having a user-space setting to determine
transaction behavior is a non-starter.
From a design perspective, there are some subtle tradeoffs that need to be
considered here, including weighing the cost/benefit of "always commit",
and ensuring that manual transaction control will continue to work for
those that need every last nanosecond of performance.
On the flipside - the existing behavior works, as long as you understand
what "works" means. This existing behavior could certainly be better,
though; in the 1.2 timeframe we can give this the serious discussion it
requires.
--
Ticket URL: <http://code.djangoproject.com/ticket/9964#comment:15>
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 [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
