Removed references to changes made in 1.2.

Note that the SQL recorded here may be :ref:`incorrectly quoted under SQLite

<sqlite-connection-queries>`.

.. versionadded:: 1.2

If you are using :doc:`multiple databases</topics/db/multi-db>`, you can use the

same interface on each member of the ``connections`` dictionary::

.. method:: Field.db_type(self, connection)

.. versionadded:: 1.2

   The ``connection`` argument was added to support multiple databases.

Returns the database column data type for the :class:`~django.db.models.Field`,

taking into account the connection object, and the settings associated with it.

.. method:: Field.get_prep_value(self, value)

.. versionadded:: 1.2

   This method was factored out of ``get_db_prep_value()``

This is the reverse of :meth:`.to_python` when working with the

database backends (as opposed to serialization). The ``value``

parameter is the current value of the model's attribute (a field has

.. method:: Field.get_db_prep_value(self, value, connection, prepared=False)

.. versionadded:: 1.2

   The ``connection`` and ``prepared`` arguments were added to support multiple databases.

Some data types (for example, dates) need to be in a specific format

before they can be used by a database backend.

:meth:`.get_db_prep_value` is the method where those conversions should

.. method:: Field.get_db_prep_save(self, value, connection)

.. versionadded:: 1.2

   The ``connection`` argument was added to support multiple databases.

Same as the above, but called when the Field value must be *saved* to

the database. As the default implementation just calls

:meth:`.get_db_prep_value`, you shouldn't need to implement this method

.. method:: Field.get_prep_lookup(self, lookup_type, value)

.. versionadded:: 1.2

   This method was factored out of ``get_db_prep_lookup()``

:meth:`.get_prep_lookup` performs the first phase of lookup preparation,

performing generic data validity checks

.. method:: Field.get_db_prep_lookup(self, lookup_type, value, connection, prepared=False)

.. versionadded:: 1.2

   The ``connection`` and ``prepared`` arguments were added to support multiple databases.

Performs any database-specific data conversions required by a lookup.

As with :meth:`.get_db_prep_value`, the specific connection that will

be used for the query is passed as the ``connection`` parameter.

Thread-safety considerations

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

.. versionadded:: 1.2

Once a node is parsed, its ``render`` method may be called any number of times.

Since Django is sometimes run in multi-threaded environments, a single node may

be simultaneously rendering with different contexts in response to two separate

Javascript patches

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

.. versionadded:: 1.2

Django's admin system leverages the jQuery framework to increase the

capabilities of the admin interface. In conjunction, there is an emphasis on

admin javascript performance and minimizing overall admin media file size.

.. attribute:: ModelAdmin.actions_selection_counter

    .. versionadded:: 1.2

    Controls whether a selection counter is display next to the action dropdown.

    By default, the admin changelist will display it

    (``actions_selection_counter = True``).

            fields = ('url', 'title', 'content')

    In the above example, only the fields ``url``, ``title`` and ``content``

    will be displayed, sequentially, in the form.

    .. versionadded:: 1.2

    ``fields`` can contain values defined in :attr:`ModelAdmin.readonly_fields`

    to be displayed as read-only.

    will be displayed, sequentially, in the form. ``fields`` can contain

    values defined in :attr:`ModelAdmin.readonly_fields` to be displayed as

    read-only.

    .. versionadded:: 1.4

            'fields': (('first_name', 'last_name'), 'address', 'city', 'state'),

            }

        .. versionadded:: 1.2

        ``fields`` can contain values defined in

        :attr:`~ModelAdmin.readonly_fields` to be displayed as read-only.

.. attribute:: ModelAdmin.get_changelist

    .. versionchanged:: 1.2

    Returns the Changelist class to be used for listing. By default,

    ``django.contrib.admin.views.main.ChangeList`` is used. By inheriting this

    class you can change the behavior of the listing.

.. attribute:: ModelAdmin.readonly_fields

    .. versionadded:: 1.2

    By default the admin shows all fields as editable. Any fields in this

    option (which should be a ``list`` or ``tuple``) will display its data

    as-is and non-editable. This option behaves nearly identical to

.. attribute:: ModelAdmin.add_form_template

    .. versionadded:: 1.2

    Path to a custom template, used by :meth:`add_view`.

.. attribute:: ModelAdmin.change_form_template

.. attribute:: ModelAdmin.delete_selected_confirmation_template

    .. versionadded:: 1.2

    Path to a custom template, used by the :meth:`delete_selected`

    action method for displaying a confirmation page when deleting one

    or more objects. See the :doc:`actions

.. method:: ModelAdmin.get_readonly_fields(self, request, obj=None)

    .. versionadded:: 1.2

    The ``get_readonly_fields`` method is given the ``HttpRequest`` and the

    ``obj`` being edited (or ``None`` on an add form) and is expected to return

    a ``list`` or ``tuple`` of field names that will be displayed as read-only,

- :attr:`~InlineModelAdmin.form`

- :attr:`~ModelAdmin.fieldsets`

- :attr:`~ModelAdmin.fields`

- :attr:`~ModelAdmin.formfield_overrides`

- :attr:`~ModelAdmin.exclude`

- :attr:`~ModelAdmin.filter_horizontal`

- :attr:`~ModelAdmin.filter_vertical`

- :attr:`~ModelAdmin.prepopulated_fields`

- :attr:`~ModelAdmin.radio_fields`

- :attr:`~ModelAdmin.readonly_fields`

- :attr:`~InlineModelAdmin.raw_id_fields`

- :meth:`~ModelAdmin.formfield_for_foreignkey`

- :meth:`~ModelAdmin.formfield_for_manytomany`

.. versionadded:: 1.2

- :attr:`~ModelAdmin.readonly_fields`

- :attr:`~ModelAdmin.formfield_overrides`

.. versionadded:: 1.3

- :attr:`~ModelAdmin.ordering`

    :doc:`formsets documentation </topics/forms/formsets>` for more

    information.

    .. versionadded:: 1.2

    For users with JavaScript-enabled browsers, an "Add another" link is

    provided to enable any number of additional inlines to be added in addition

    to those provided as a result of the ``extra`` argument.

Working with many-to-many models

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

.. versionadded:: 1.2

By default, admin widgets for many-to-many relations will be displayed

on whichever model contains the actual reference to the

:class:`~django.db.models.ManyToManyField`. Depending on your ``ModelAdmin``

.. attribute:: AdminSite.logout_template

    .. versionadded:: 1.2

    Path to a custom template that will be used by the admin site logout view.

.. attribute:: AdminSite.password_change_template

    .. versionadded:: 1.2

    Path to a custom template that will be used by the admin site password

    change view.

.. attribute:: AdminSite.password_change_done_template

    .. versionadded:: 1.2

    Path to a custom template that will be used by the admin site password

    change done view.