#10088: for_share() as well as for_update() addition to Model.QuerySet
------------------------------------------+---------------------------------
Reporter: epandurski | 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
Status: new | Milestone: post-1.0
Component: Database layer (models, ORM) | Version: 1.0
Keywords: | Stage: Unreviewed
Has_patch: 0 |
------------------------------------------+---------------------------------
Ticket #2705 is a very good idea I think.
PostgreSQL supports SELECT ... FOR SHARE locking mode, which is basically
the same as FOR UPDATE mode but it does not conflicts with other
transaction
having obtained FOR SHARE mode for the row.
(see http://www.postgresql.org/docs/8.3/static/sql-select.html#SQL-FOR-
UPDATE-SHARE)
It very useful if you need to be sure that your selected rows are not
modified since you have read them (which is true for almost every complex
transaction).
I am not sure if MySQL has this feature but in PostgreSQL it first-class
citizen so
I believe for_share() and for_update() has to be implemented together.
--
Ticket URL: <http://code.djangoproject.com/ticket/10088>
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
-~----------~----~----~----~------~----~------~--~---
