mirror of
https://github.com/django/django.git
synced 2025-10-24 14:16:09 +00:00
Fixed #29339 -- Added result caching to RawQuerySet.
This commit is contained in:
@@ -401,6 +401,9 @@ Miscellaneous
|
||||
* The admin CSS class ``field-box`` is renamed to ``fieldBox`` to prevent
|
||||
conflicts with the class given to model fields named "box".
|
||||
|
||||
* ``QuerySet.raw()`` now caches its results like regular querysets. Use
|
||||
``iterator()`` if you don't want caching.
|
||||
|
||||
.. _deprecated-features-2.1:
|
||||
|
||||
Features deprecated in 2.1
|
||||
|
||||
@@ -91,10 +91,7 @@ options that make it very powerful.
|
||||
:class:`~django.db.models.query.QuerySet`, ``RawQuerySet`` doesn't
|
||||
implement all methods you can use with ``QuerySet``. For example,
|
||||
``__bool__()`` and ``__len__()`` are not defined in ``RawQuerySet``, and
|
||||
thus all ``RawQuerySet`` instances are considered ``True``. The reason
|
||||
these methods are not implemented in ``RawQuerySet`` is that implementing
|
||||
them without internal caching would be a performance drawback and adding
|
||||
such caching would be backward incompatible.
|
||||
thus all ``RawQuerySet`` instances are considered ``True``.
|
||||
|
||||
Mapping query fields to model fields
|
||||
------------------------------------
|
||||
|
||||
Reference in New Issue
Block a user