      :meth:`~django.db.models.Model.save()` for more details.
  
  ``using()``
  ~~~~~~~~~~~
  
  .. method:: using(alias)
  
 
</s> remove The ``only()`` method is more or less the opposite of :meth:`defer()`. You call
it with the fields that should *not* be deferred when retrieving a model.  If
you have a model where almost all the fields need to be deferred, using
 </s> add The ``only()`` method is essentially the opposite of :meth:`defer`. Only the
fields passed into this method and that are *not* already specified as deferred
are loaded immediately when the queryset is evaluated.

If you have a model where almost all the fields need to be deferred, using </s> remove     # Final result loads headline and body immediately (only() replaces any
    # existing set of fields).
 </s> add     # Final result loads headline immediately.
.. note::

    When using :meth:`defer` after ``only()`` the fields in :meth:`defer` will
    override ``only()`` for fields that are listed in both.

      :meth:`~django.db.models.Model.save()` for more details.
  
.. note::

    When using :meth:`defer` after ``only()`` the fields in :meth:`defer` will
    override ``only()`` for fields that are listed in both.

  ``using()``
  ~~~~~~~~~~~
  
  .. method:: using(alias)
  
keep add keep keep keep keep keep
 Fixed #24048 -- Corrected QuerySet.only() docs about interaction with defer(). 
docs/ref/models/querysets.txt