  ~~~~~~~~~~
  
  .. method:: only(*fields)
  
  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
  ``only()`` to specify the complementary set of fields can result in simpler
  code.
  
  Suppose you have a model with fields ``name``, ``age`` and ``biography``. The
  following two querysets are the same, in terms of deferred fields::
 
</s> remove     # Final result loads headline and body immediately (only() replaces any
    # existing set of fields).
 </s> add     # Final result loads headline immediately.
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
  ~~~~~~~~~~
  
  .. method:: only(*fields)
  
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
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
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
  ``only()`` to specify the complementary set of fields can result in simpler
  code.
  
  Suppose you have a model with fields ``name``, ``age`` and ``biography``. The
  following two querysets are the same, in terms of deferred fields::
keep keep keep keep replace replace replace keep keep keep keep keep
 Fixed #24048 -- Corrected QuerySet.only() docs about interaction with defer(). 
docs/ref/models/querysets.txt