Fixed #3094 -- Accelerated deprecation of XMLField, since it hasn't served any...

        models.TextField : OFTString,

        models.URLField : OFTString,

        USStateField : OFTString,

        # This is a reminder that XMLField is deprecated

        # and this needs to be removed in 1.4

        models.XMLField : OFTString,

        models.SmallIntegerField : (OFTInteger, OFTReal, OFTString),

        models.PositiveSmallIntegerField : (OFTInteger, OFTReal, OFTString),

        #

        # A Field class can implement the get_internal_type() method to specify

        # which *preexisting* Django Field class it's most similar to -- i.e.,

        # an XMLField is represented by a TEXT column type, which is the same

        # as the TextField Django field type, which means XMLField's

        # a custom field might be represented by a TEXT column type, which is the

        # same as the TextField Django field type, which means the custom field's

        # get_internal_type() returns 'TextField'.

        #

        # But the limitation of the get_internal_type() / data_types approach

    description = _("XML text")

    def __init__(self, verbose_name=None, name=None, schema_path=None, **kwargs):

        import warnings

        warnings.warn("Use of XMLField has been deprecated; please use TextField instead.",

                      DeprecationWarning)

        self.schema_path = schema_path

        Field.__init__(self, verbose_name, name, **kwargs)

          removed.

        * The ``get_db_prep_save``, ``get_db_prep_value`` and

          ``get_db_prep_lookup`` methods on Field were modified in 1.2 to support

          multiple databases. In 1.4, the support functions that allow methods

          with the old prototype to continue working will be removed.

          ``get_db_prep_lookup`` methods on Field were modified in 1.2

          to support multiple databases. In 1.4, the support functions

          that allow methods with the old prototype to continue

          working will be removed.

        * The ``Message`` model (in ``django.contrib.auth``), its related

          manager in the ``User`` model (``user.message_set``), and the

          with a trailing slash to ensure there is a consistent way to

          combine paths in templates.

        * ``django.db.models.fields.XMLField`` will be removed. This was

          deprecated as part of the 1.3 release. An accelerated deprecation

          schedule has been used because the field hasn't performed any role

          beyond that of a simple ``TextField`` since the removal of oldforms.

          All uses of ``XMLField`` can be replaced with ``TextField``.

    * 1.5

        * The ``mod_python`` request handler has been deprecated since the 1.3

          release. The ``mod_wsgi`` handler should be used instead.

``XMLField``

------------

.. deprecated:: 1.3

   ``XMLField`` is deprecated. Use TextField instead.

.. class:: XMLField(schema_path=None, [**options])

A :class:`TextField` that checks that the value is valid XML that matches a

given schema. Takes one required argument:

A :class:`TextField` that stores XML data and a path to a schema. Takes one

optional argument:

.. attribute:: schema_path

    The filesystem path to a RelaxNG_ schema against which to validate the

    field.

    The filesystem path to a schema for the field.

.. _RelaxNG: http://www.relaxng.org/

Relationship fields

===================

moved to ``django.contrib.auth.context_processors``, along with the

``PermLookupDict`` support class. The new classes are functionally

identical to their old versions; only the module location has changed.

Removal of ``XMLField``

~~~~~~~~~~~~~~~~~~~~~~~

When Django was first released, Django included an ``XMLField`` that

performed automatic XML validation for any field input. However, this

validation function hasn't been performed since the introduction of

``newforms``, prior to the 1.0 release. As a result, ``XMLField`` as

currently implemented is functionally indistinguishable from a simple

``TextField``.

For this reason, Django 1.3 has fast-tracked the deprecation of

``XMLField`` -- instead of a two-release deprecation, ``XMLField``

will be removed entirely in Django 1.4.

It's easy to update your code to accommodate this change -- just

replace all uses of ``XMLField`` with ``TextField``, and remove the

``schema_path`` keyword argument (if it is specified).