#2705: [patch] Add optional FOR UPDATE clause to QuerySets
---------------------------------------------------+------------------------
Reporter: Hawkeye | Owner: nobody
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
---------------------------------------------------+------------------------
Comment (by anih):
Replying to [comment:38 ikelly]:
> Update: I'm having a heck of a time nailing down exactly what's going on
with this hang issue. It reliably occurs when using the oracle backend,
but outside of Django I can't reproduce it at all; the connection does get
properly cleaned up when the deadlocked thread exits. About the only
thing I've managed to determine is that if I run {{{del
connection.connection}}} when exiting the test threads, then the issue
does not occur and the tests pass. What I can't figure out is why this is
necessary.
maybe problem is related with that select_for_update didnt set transaction
dirty? new patch have this corected(i think)
--
Ticket URL: <http://code.djangoproject.com/ticket/2705#comment:39>
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
-~----------~----~----~----~------~----~------~--~---
