  passed as the ``connection`` parameter. This allows you to use
  backend-specific conversion logic if it is required.
  
  The ``prepared`` argument describes whether or not the value has
  already been passed through :meth:`get_prep_value` conversions. When
  ``prepared`` is False, the default implementation of
  :meth:`get_db_prep_value` will call :meth:`get_prep_value` to do
  initial data conversions before performing any database-specific
  processing.
  
 
</s> remove :meth:`get_db_prep_value` will call :meth:`get_prep_value` to do
 </s> add :meth:`.get_db_prep_value` will call :meth:`.get_prep_value` to do </s> remove :meth:`get_db_prep_value` is the method where those conversions should
 </s> add :meth:`.get_db_prep_value` is the method where those conversions should </s> remove .. method:: get_db_prep_save(self, value, connection)
 </s> add .. method:: Field.get_db_prep_save(self, value, connection) </s> remove should be made in the call to :meth:`get_db_prep_value`.
 </s> add should be made in the call to :meth:`.get_db_prep_value`. </s> remove ``get_db_prep_value``, you shouldn't need to implement this method
 </s> add :meth:`.get_db_prep_value`, you shouldn't need to implement this method
already been passed through :meth:`.get_prep_value` conversions. When
  passed as the ``connection`` parameter. This allows you to use
  backend-specific conversion logic if it is required.
  
  The ``prepared`` argument describes whether or not the value has
already been passed through :meth:`.get_prep_value` conversions. When
  ``prepared`` is False, the default implementation of
  :meth:`get_db_prep_value` will call :meth:`get_prep_value` to do
  initial data conversions before performing any database-specific
  processing.
  
keep keep keep keep replace keep keep keep keep keep
 Fixed #15308 -- Sphinx/reST fixes for the Custom Model Fields docs.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@15547 bcc190cf-cafb-0310-a4f2-bffc1f526a37 
docs/howto/custom-model-fields.txt