#9964: Transaction middleware closes the transaction only when it's marked as
dirty
---------------------------------------------------+------------------------
Reporter: ishirav | Owner:
mtredinnick
Status: assigned | Milestone: 1.1
Component: Database layer (models, ORM) | Version: 1.0-beta-1
Resolution: | Keywords:
transactions
Stage: Accepted | Has_patch: 1
Needs_docs: 1 | Needs_tests: 1
Needs_better_patch: 1 |
---------------------------------------------------+------------------------
Changes (by shai):
* needs_better_patch: 0 => 1
* has_patch: 0 => 1
* needs_tests: 0 => 1
* needs_docs: 0 => 1
Comment:
The patch I just attached is not ready for inclusion and not tested, I
just want to get some feedback on the ideas:
- Take the functions affected by 'dirty' out to separate modules, each
providing a different version of them
- fast_select.py reflects current behavior
- safe.py always closes transactions
- Selection between modules is done by settings.py
- The default is fast_select (existing behavior), for backward
compatibility
- The project template is modified to select 'safe', so new projects get
that by default
- But if they need the extra performance, and are willing to pay their
dues in code diligence, they can
--
Ticket URL: <http://code.djangoproject.com/ticket/9964#comment:9>
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
-~----------~----~----~----~------~----~------~--~---
