#2705: [patch] Add optional FOR UPDATE clause to QuerySets
---------------------------------------------------+------------------------
Reporter: Hawkeye | Owner: brunobraga
Status: assigned | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by danfairs):
Apologies for the delay - holidays, sickness and the resultant backlog are
responsible for that.
While I was unable to reproduce the test failures Jacob saw directly, I
did see that there was an error with the transaction setup. This caused an
unintended commit, which explains why the `Person` created in `setUp()`
persisted unexpectedly. Once I had fixed this problem, I then started
seeing the traceback that Jacob saw.
The newest version of the patch contains these changes, and also changes
the `NOWAIT` behaviour on backends that do not support it by raising a
`DatabaseError` when a query with NOWAIT is run, as Jacob commented.
The docs have also been updated to reflect the new behaviour.
I've tested this with MySQL, PostgreSQL and SQLite, and the tests pass -
I'll test on Oracle in the next couple of days.
--
Ticket URL: <http://code.djangoproject.com/ticket/2705#comment:74>
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.
