From c92e0e47657f8c53673523428011f34ba15be7bb Mon Sep 17 00:00:00 2001 From: Jacob Kaplan-Moss Date: Wed, 20 Apr 2011 21:00:24 +0000 Subject: [PATCH] Added notes about `select_for_update` to the 1.4 release notes. git-svn-id: http://code.djangoproject.com/svn/django/trunk@16059 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/releases/1.4.txt | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/docs/releases/1.4.txt b/docs/releases/1.4.txt index 9de896d33d..674916175d 100644 --- a/docs/releases/1.4.txt +++ b/docs/releases/1.4.txt @@ -13,10 +13,21 @@ which are detailed in :doc:`our deprecation plan `. .. _new features: `What's new in Django 1.4`_ .. _backwards incompatible changes: backwards-incompatible-changes-1.4_ - What's new in Django 1.4 ======================== +``SELECT FOR UPDATE`` support +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Django 1.4 now includes a :meth:`QuerySet.select_for_update() +` method which generates a +``SELECT ... FOR UPDATE`` SQL query. This will lock rows until the end of the +transaction, meaning that other transactions cannot modify or delete rows +matched by a ``FOR UPDATE`` query. + +For more details, see the documentation for +:meth:`~django.db.models.query.QuerySet.select_for_update`. + .. _backwards-incompatible-changes-1.4: Backwards incompatible changes in 1.4