Fixed spelling in docs.

        This is a required argument.

        Specifies the underlying data type and behaviour for the array. It

        Specifies the underlying data type and behavior for the array. It

        should be an instance of a subclass of

        :class:`~django.db.models.Field`. For example, it could be an

        :class:`~django.db.models.IntegerField` or a

.. admonition:: Multidimensional arrays with indexes and slices

    PostgreSQL has some rather esoteric behaviour when using indexes and slices

    PostgreSQL has some rather esoteric behavior when using indexes and slices

    on multidimensional arrays. It will always work to use indexes to reach

    down to the final underlying data, but most other slices behave strangely

    at the database level and cannot be supported in a logical, consistent

    Django is, and will continue to be, a database-agnostic web framework. We

    would encourage those writing reusable applications for the Django

    community to write database-agnostic code where practical. However, we

    recognise that real world projects written using Django need not be

    recognize that real world projects written using Django need not be

    database-agnostic. In fact, once a project reaches a given size changing

    the underlying data store is already a significant challenge and is likely

    to require changing the code base in some ways to handle differences

    When Django searches for a certain format, it will go through all given

    Python paths until it finds a module that actually defines the given

    format. This means that formats defined in packages farther up in the list

    will take precendence over the same formats in packages farther down.

    will take precedence over the same formats in packages farther down.

Available formats are :setting:`DATE_FORMAT`, :setting:`TIME_FORMAT`,

:setting:`DATETIME_FORMAT`, :setting:`YEAR_MONTH_FORMAT`,

Gunicorn

gz

GZip

gzipped

hackish

handheld

hardcode