  .. versionchanged:: 1.5
  
  .. note::
  
      When calling :meth:`~django.db.models.Model.save()` for instances with
      deferred fields, only the loaded fields will be saved. See
      :meth:`~django.db.models.Model.save()` for more details.
  
  using
  ~~~~~
  
  .. method:: using(alias)
 
</s> remove .. note::
 </s> add     Using :meth:`only` and omitting a field requested using
    :meth:`select_related` is an error as well. </s> remove options. Also note that using :meth:`only` and omitting a field requested
using :meth:`select_related` is an error as well.
 </s> add options. </s> remove Some fields in a model won't be deferred, even if you ask for them. You can
never defer the loading of the primary key. If you are using
:meth:`select_related()` to retrieve related models, you shouldn't defer the
loading of the field that connects from the primary model to the related
one, doing so will result in an error.
 </s> add     Some fields in a model won't be deferred, even if you ask for them. You can
    never defer the loading of the primary key. If you are using
    :meth:`select_related()` to retrieve related models, you shouldn't defer the
    loading of the field that connects from the primary model to the related
    one, doing so will result in an error. </s> remove     The ``widgets`` and the ``validate_max`` parameters were added.
 </s> add         The ``widgets`` and the ``validate_max`` parameters were added. </s> remove         Historically, this parameter was only called ``mimetype`` (now
        deprecated), but since this is actually the value included in the HTTP
        ``Content-Type`` header, it can also include the character set
        encoding, which makes it more than just a MIME type specification. If
        ``mimetype`` is specified (not ``None``), that value is used.
        Otherwise, ``content_type`` is used. If neither is given,
        :setting:`DEFAULT_CONTENT_TYPE` is used.
 </s> add             Historically, this parameter was only called ``mimetype`` (now
            deprecated), but since this is actually the value included in the HTTP
            ``Content-Type`` header, it can also include the character set
            encoding, which makes it more than just a MIME type specification. If
            ``mimetype`` is specified (not ``None``), that value is used.
            Otherwise, ``content_type`` is used. If neither is given,
            :setting:`DEFAULT_CONTENT_TYPE` is used.
    .. note::

        When calling :meth:`~django.db.models.Model.save()` for instances with
        deferred fields, only the loaded fields will be saved. See
        :meth:`~django.db.models.Model.save()` for more details.
  .. versionchanged:: 1.5
  
  .. note::
  
    .. note::

        When calling :meth:`~django.db.models.Model.save()` for instances with
        deferred fields, only the loaded fields will be saved. See
        :meth:`~django.db.models.Model.save()` for more details.
    .. note::

        When calling :meth:`~django.db.models.Model.save()` for instances with
        deferred fields, only the loaded fields will be saved. See
        :meth:`~django.db.models.Model.save()` for more details.
    .. note::

        When calling :meth:`~django.db.models.Model.save()` for instances with
        deferred fields, only the loaded fields will be saved. See
        :meth:`~django.db.models.Model.save()` for more details.
  
  using
  ~~~~~
  
  .. method:: using(alias)
keep keep keep keep replace replace replace keep keep keep keep keep
 Adapted uses of versionchanged/versionadded to the new form.

Refs #20104. 
docs/ref/models/querysets.txt