#2705: Add optional FOR UPDATE clause to 'get' database operations
------------------------------+---------------------------------------------
Reporter: Hawkeye | Owner: adrian
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Database wrapper | Version:
Severity: normal | Resolution:
Keywords: |
------------------------------+---------------------------------------------
Comment (by [EMAIL PROTECTED]):
My original proposal was grossly defect (it just meant to illustrate the
idea).
What I really meant was adding `for_update()` as a method to QuerySet,
returning a QuerySet (like filter, distinct, etc.)
So, the example should of course be the other way around:
{{{
something = models.Something.objects.for_update().get(id=333)
}}}
or, easier to understand,
{{{
something = models.Something.objects.filter(id=333).for_update().get()
}}}
--
Ticket URL: <http://code.djangoproject.com/ticket/2705>
Django <http://code.djangoproject.org/>
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
-~----------~----~----~----~------~----~------~--~---