mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-08-04 10:59:45 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

Removed versionadded/changed annotations for 1.9.

Browse source
This commit is contained in:
Tim Graham 2016-05-20 10:50:51 -04:00
parent 1915a7e5c5
commit 46a38307c2
67 changed files with 15 additions and 731 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/topics/db/queries.txt
View file

@ -899,10 +899,6 @@ the number of deletions per object type. Example::
>>> e.delete()
(1, {'weblog.Entry': 1})
.. versionchanged:: 1.9
The return value describing the number of objects deleted was added.
You can also delete objects in bulk. Every
:class:`~django.db.models.query.QuerySet` has a
:meth:`~django.db.models.query.QuerySet.delete` method, which deletes all
@ -924,10 +920,6 @@ object individually) rather than using the bulk
:meth:`~django.db.models.query.QuerySet.delete` method of a
:class:`~django.db.models.query.QuerySet`.
.. versionchanged:: 1.9
The return value describing the number of objects deleted was added.
When Django deletes an object, by default it emulates the behavior of the SQL
constraint ``ON DELETE CASCADE`` -- in other words, any objects which had
foreign keys pointing at the object to be deleted will be deleted along with

2
docs/topics/db/transactions.txt
View file

@ -254,8 +254,6 @@ something really strange.
Performing actions after commit
===============================
.. versionadded:: 1.9
Sometimes you need to perform an action related to the current database
transaction, but only if the transaction successfully commits. Examples might
include a `Celery`_ task, an email notification, or a cache invalidation.