Removed versionadded/changed annotations for 5.0.

This also removes remaining versionadded/changed annotations for older
versions.
This commit is contained in:
Natalia 2024-05-03 14:39:43 -03:00 committed by nessita
parent ec44247f59
commit 05cce083ad
44 changed files with 0 additions and 379 deletions

View file

@ -1160,12 +1160,6 @@ supports prefetching of
queryset for each ``ContentType`` must be provided in the ``querysets``
parameter of :class:`~django.contrib.contenttypes.prefetch.GenericPrefetch`.
.. versionchanged:: 5.0
Support for prefetching
:class:`~django.contrib.contenttypes.fields.GenericForeignKey` with
non-homogeneous set of results was added.
For example, suppose you have these models::
from django.db import models
@ -2114,13 +2108,6 @@ SQL equivalent:
2
)
.. versionchanged:: 5.0
In older versions, on databases without native support for the SQL
``XOR`` operator, ``XOR`` returned rows that were matched by exactly
one operand. The previous behavior was not consistent with MySQL,
MariaDB, and Python behavior.
Methods that do not return ``QuerySet``\s
-----------------------------------------
@ -2402,10 +2389,6 @@ Like :meth:`get_or_create` and :meth:`create`, if you're using manually
specified primary keys and an object needs to be created but the key already
exists in the database, an :exc:`~django.db.IntegrityError` is raised.
.. versionchanged:: 5.0
The ``create_defaults`` argument was added.
``bulk_create()``
~~~~~~~~~~~~~~~~~
@ -2470,11 +2453,6 @@ be in conflict must be provided.
Enabling the ``ignore_conflicts`` parameter disables setting the primary key on
each model instance (if the database normally supports it).
.. versionchanged:: 5.0
In older versions, enabling the ``update_conflicts`` parameter prevented
setting the primary key on each model instance.
.. warning::
On MySQL and MariaDB, setting the ``ignore_conflicts`` parameter to
@ -2629,11 +2607,6 @@ evaluated will force it to evaluate again, repeating the query.
long as ``chunk_size`` is given. Larger values will necessitate fewer queries
to accomplish the prefetching at the cost of greater memory usage.
.. versionchanged:: 5.0
Support for ``aiterator()`` with previous calls to ``prefetch_related()``
was added.
On some databases (e.g. Oracle, `SQLite
<https://www.sqlite.org/limits.html#max_variable_number>`_), the maximum number
of terms in an SQL ``IN`` clause might be limited. Hence values below this
@ -4162,10 +4135,6 @@ When using multiple databases with ``prefetch_related_objects``, the prefetch
query will use the database associated with the model instance. This can be
overridden by using a custom queryset in a related lookup.
.. versionchanged:: 5.0
``aprefetch_related_objects()`` function was added.
``FilteredRelation()`` objects
------------------------------