  
  exact
  ~~~~~
  
  Exact match. If the value provided for comparison is ``None``, it will 
  be interpreted as an SQL ``NULL`` (See isnull_ for more details).  
  
  Examples::
  
      Entry.objects.get(id__exact=14)
      Entry.objects.get(id__exact=None)
 
</s> remove See _`How Django knows to UPDATE vs. INSERT`, below, for the reason this
 </s> add See `How Django knows to UPDATE vs. INSERT`_, below, for the reason this </s> remove These methods do not use a cache (see _`Caching and QuerySets` below). Rather,
 </s> add These methods do not use a cache (see `Caching and QuerySets`_ below). Rather,
Exact match. If the value provided for comparison is ``None``, it will
be interpreted as an SQL ``NULL`` (See isnull_ for more details).
  
  exact
  ~~~~~
  
Exact match. If the value provided for comparison is ``None``, it will
be interpreted as an SQL ``NULL`` (See isnull_ for more details).
Exact match. If the value provided for comparison is ``None``, it will
be interpreted as an SQL ``NULL`` (See isnull_ for more details).
  
  Examples::
  
      Entry.objects.get(id__exact=14)
      Entry.objects.get(id__exact=None)
keep keep keep keep replace replace keep keep keep keep keep
 Fixed #4175 -- Fixed a couple of ReST markup errors. Thanks, Matt McClanahan.


git-svn-id: http://code.djangoproject.com/svn/django/trunk@5120 bcc190cf-cafb-0310-a4f2-bffc1f526a37 
docs/db-api.txt