#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: 1 |
---------------------------------------------------+------------------------
Changes (by brunobraga):
* cc: ftmo (added)
Comment:
We have worked with [ftmo] to update previous patches according to newest
releases, but I see it is pointless to keep doing that every time...
Instead, we should push this to the main stream, but I don't know what
still needs to be done for it to be properly accepted.
I would like to flag this for review by the committers (forward to "ready
for checkin"), and if there is anything missing, let us know, so we can
work on it and finalize this.
For reference, we are using the latest 1.2.0 patch in production
environment for almost 6 months now, without any problems.
Thanks in advance,
--
Ticket URL: <http://code.djangoproject.com/ticket/2705#comment:61>
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.
