  
  ``get_db_prep_*()`` methods on ``Field``
  ----------------------------------------
  
  Prior to 1.2, a custom ``Field`` had the option of defining several
  functions to support conversion of Python values into
  database-compatible values. A custom field might look something like::
  
      class CustomModelField(models.Field):
          # ...
  
 
</s> remove iterating over __dict__ to obtain a list of fields, you must now
filter the ``_state`` attribute out of ``__dict__``.
 </s> add iterating over ``__dict__`` to obtain a list of fields, you must now
be prepared to handle or filter out the ``_state`` attribute. </s> remove definitions to use the new prototype now, just to get it over with.
 </s> add definitions to use the new prototype as soon as possible. </s> remove    requires the use of the csrf_token template tag in the template. If you
 </s> add    requires the use of the ``csrf_token`` template tag in the template. If you </s> remove Any existing Django settings file will continue to work as expected until
Django 1.4. Until then, old-style database settings will be automatically
translated to the new-style format.
 </s> add Any existing Django settings file will continue to work as expected
until Django 1.4. Until then, old-style database settings will be
automatically translated to the new-style format. </s> remove Prior to Django 1.1, Django used a number of settings to control access to a
single database. Django 1.2 introduces support for multiple databases, and as
a result, the way you define database settings has changed.
 </s> add Prior to Django 1.1, Django used a number of settings to control
access to a single database. Django 1.2 introduces support for
multiple databases, and as a result the way you define database
settings has changed.
Prior to Django 1.2, a custom ``Field`` had the option of defining
several functions to support conversion of Python values into
  
  ``get_db_prep_*()`` methods on ``Field``
  ----------------------------------------
  
Prior to Django 1.2, a custom ``Field`` had the option of defining
several functions to support conversion of Python values into
Prior to Django 1.2, a custom ``Field`` had the option of defining
several functions to support conversion of Python values into
  database-compatible values. A custom field might look something like::
  
      class CustomModelField(models.Field):
          # ...
  
keep keep keep keep replace replace keep keep keep keep keep
 Update 1.2 release notes in anticipation of final release.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@13259 bcc190cf-cafb-0310-a4f2-bffc1f526a37 
docs/releases/1.2.txt