#15383: TransactionManagementError although I've rollbacked the transaction
--------------------------------------------------------+-------------------
Reporter: coopkont@… | Owner:
nobody
Status: closed | Milestone: 1.3
Component: Database layer (models, ORM) | Version: SVN
Resolution: invalid | Keywords:
transaction
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 |
--------------------------------------------------------+-------------------
Comment (by anonymous):
Are you happy with this change ?
I am really really sorry but I refuse to believe that this is a feature
instead of a bug.
What about custom tags in templates that run select queries in the db ?
What about display logic that is implemented after the transactional part
of a request is finished ?
I wasn't even aware that the transaction persists for the whole
connection, I thought that the transaction was committed/rollbacked when
the actual commands are called. This it self is really bad as it probably
leaves the transaction open for longer than needed, locking tables
throughout the whole request !
I do appreciate that this is a documented change but it completely makes
transaction management in django unusable. I will seek advice in the
forums !
--
Ticket URL: <http://code.djangoproject.com/ticket/15383#comment:3>
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-updates@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.
