#10088: for_share() as well as for_update() addition to Model.QuerySet
---------------------------------------------------+------------------------
Reporter: epandurski | Owner:
Status: new | Milestone: post-1.0
Component: Database layer (models, ORM) | Version: 1.0
Resolution: | Keywords:
Stage: Design decision needed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by mtredinnick):
* owner: m...@noris.de, rajeev.sebast...@gmail.com, v...@stream.net.ua,
sebast...@e-ti.net, justin.fi...@gmail.com,
lidaob...@gmail.com, jdem...@gmail.com,
walle...@gmail.com, sebast...@sspaeth.de =>
* stage: Unreviewed => Design decision needed
Comment:
Removing the ''list'' of people in the assigned field.
This is fairly orthogonal to `for_update()`. Django isn't meant to provide
wrappers for every database feature under the sun, so we might not do
this. Worth thinking about, however.
--
Ticket URL: <http://code.djangoproject.com/ticket/10088#comment:2>
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
-~----------~----~----~----~------~----~------~--~---
