  
      b4 = Blog(id=3, name='Not Cheddar', tagline='Anything but cheese.')
      b4.save()  # Overrides the previous blog with ID=3!
  
  See _`How Django knows to UPDATE vs. INSERT`, below, for the reason this
  happens.
  
  Explicitly specifying auto-primary-key values is mostly useful for bulk-saving
  objects, when you're confident you won't have primary-key collision.
  
 
</s> remove Exact match. If the value provided for comparison is ``None``, it will 
be interpreted as an SQL ``NULL`` (See isnull_ for more details).  
 </s> add Exact match. If the value provided for comparison is ``None``, it will
be interpreted as an SQL ``NULL`` (See isnull_ for more details). </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,
See `How Django knows to UPDATE vs. INSERT`_, below, for the reason this
  
      b4 = Blog(id=3, name='Not Cheddar', tagline='Anything but cheese.')
      b4.save()  # Overrides the previous blog with ID=3!
  
See `How Django knows to UPDATE vs. INSERT`_, below, for the reason this
  happens.
  
  Explicitly specifying auto-primary-key values is mostly useful for bulk-saving
  objects, when you're confident you won't have primary-key collision.
  
keep keep keep keep 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