mirror of
https://github.com/django/django.git
synced 2025-01-03 06:55:47 +00:00
Fixed spelling in docs.
This commit is contained in:
parent
2ea1e70b85
commit
4b57e203fe
@ -21,7 +21,7 @@ ArrayField
|
|||||||
|
|
||||||
This is a required argument.
|
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
|
should be an instance of a subclass of
|
||||||
:class:`~django.db.models.Field`. For example, it could be an
|
:class:`~django.db.models.Field`. For example, it could be an
|
||||||
:class:`~django.db.models.IntegerField` or a
|
:class:`~django.db.models.IntegerField` or a
|
||||||
@ -227,7 +227,7 @@ lookups available after the transform do not change. For example::
|
|||||||
|
|
||||||
.. admonition:: Multidimensional arrays with indexes and slices
|
.. 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
|
on multidimensional arrays. It will always work to use indexes to reach
|
||||||
down to the final underlying data, but most other slices behave strangely
|
down to the final underlying data, but most other slices behave strangely
|
||||||
at the database level and cannot be supported in a logical, consistent
|
at the database level and cannot be supported in a logical, consistent
|
||||||
|
@ -9,12 +9,12 @@ a number of PostgreSQL specific data types.
|
|||||||
Django is, and will continue to be, a database-agnostic web framework. We
|
Django is, and will continue to be, a database-agnostic web framework. We
|
||||||
would encourage those writing reusable applications for the Django
|
would encourage those writing reusable applications for the Django
|
||||||
community to write database-agnostic code where practical. However, we
|
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
|
database-agnostic. In fact, once a project reaches a given size changing
|
||||||
the underlying data store is already a significant challenge and is likely
|
the underlying data store is already a significant challenge and is likely
|
||||||
to require changing the code base in some ways to handle differences
|
to require changing the code base in some ways to handle differences
|
||||||
between the data stores.
|
between the data stores.
|
||||||
|
|
||||||
Django provides support for a number of data types which will
|
Django provides support for a number of data types which will
|
||||||
only work with PostgreSQL. There is no fundamental reason why (for example)
|
only work with PostgreSQL. There is no fundamental reason why (for example)
|
||||||
a ``contrib.mysql`` module does not exist, except that PostgreSQL has the
|
a ``contrib.mysql`` module does not exist, except that PostgreSQL has the
|
||||||
|
@ -1391,7 +1391,7 @@ like::
|
|||||||
When Django searches for a certain format, it will go through all given
|
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
|
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
|
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`,
|
Available formats are :setting:`DATE_FORMAT`, :setting:`TIME_FORMAT`,
|
||||||
:setting:`DATETIME_FORMAT`, :setting:`YEAR_MONTH_FORMAT`,
|
:setting:`DATETIME_FORMAT`, :setting:`YEAR_MONTH_FORMAT`,
|
||||||
|
@ -244,6 +244,7 @@ gunicorn
|
|||||||
Gunicorn
|
Gunicorn
|
||||||
gz
|
gz
|
||||||
GZip
|
GZip
|
||||||
|
gzipped
|
||||||
hackish
|
hackish
|
||||||
handheld
|
handheld
|
||||||
hardcode
|
hardcode
|
||||||
|
Loading…
Reference in New Issue
Block a user