[1.6.x] Updated MySQL links to version 5.6.

MySQL's spatial extensions only support bounding box operations

(what MySQL calls minimum bounding rectangles, or MBR).  Specifically,

`MySQL does not conform to the OGC standard <http://dev.mysql.com/doc/refman/5.1/en/functions-for-testing-spatial-relations-between-geometric-objects.html>`_:

`MySQL does not conform to the OGC standard

<http://dev.mysql.com/doc/refman/5.6/en/spatial-relation-functions.html>`_:

    Currently, MySQL does not implement these functions

    [``Contains``, ``Crosses``, ``Disjoint``, ``Intersects``, ``Overlaps``,

Creating and Saving Geographic Models

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

Here is an example of how to create a geometry object (assuming the ``Zipcode``

model)::

.. [#fngeojson] *See* Howard Butler, Martin Daly, Allan Doyle, Tim Schaub, & Christopher Schmidt, `The GeoJSON Format Specification <http://geojson.org/geojson-spec.html>`_, Revision 1.0 (June 16, 2008).

.. [#fndistsphere14] *See* `PostGIS 1.4 documentation <http://postgis.refractions.net/documentation/manual-1.4/ST_Distance_Sphere.html>`_ on ``ST_distance_sphere``.

.. [#fndistsphere15] *See* `PostGIS 1.5 documentation <http://postgis.refractions.net/documentation/manual-1.5/ST_Distance_Sphere.html>`_ on ``ST_distance_sphere``.

.. [#fnmysqlidx] *See* `Creating Spatial Indexes <http://dev.mysql.com/doc/refman/5.1/en/creating-spatial-indexes.html>`_

   in the MySQL 5.1 Reference Manual:

.. [#fnmysqlidx] *See* `Creating Spatial Indexes <http://dev.mysql.com/doc/refman/5.6/en/creating-spatial-indexes.html>`_

   in the MySQL Reference Manual:

       For MyISAM tables, ``SPATIAL INDEX`` creates an R-tree index. For storage

       engines that support nonspatial indexing of spatial columns, the engine

Django supports MySQL 5.0.3 and higher.

`MySQL 5.0`_ adds the ``information_schema`` database, which contains detailed

data on all database schema. Django's ``inspectdb`` feature uses it.

Django's ``inspectdb`` feature uses the ``information_schema`` database, which

contains detailed data on all database schemas.

.. versionchanged:: 1.5

to be aware of the fact that the two latter ones aren't actually enforced by

MySQL when using the MyISAM storage engine, see the next section.

.. _MySQL: http://www.mysql.com/

.. _MySQL 5.0: http://dev.mysql.com/doc/refman/5.0/en/index.html

.. _mysql-storage-engines:

Storage engines

        1005, "Can't create table '\\db_name\\.#sql-4a8_ab' (errno: 150)"

    )

.. _storage engines: http://dev.mysql.com/doc/refman/5.5/en/storage-engines.html

.. _MyISAM: http://dev.mysql.com/doc/refman/5.5/en/myisam-storage-engine.html

.. _InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-storage-engine.html

.. _storage engines: http://dev.mysql.com/doc/refman/5.6/en/storage-engines.html

.. _MyISAM: http://dev.mysql.com/doc/refman/5.6/en/myisam-storage-engine.html

.. _InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-storage-engine.html

.. [#] Unless this was changed by the packager of your MySQL package. We've

   had reports that the Windows Community Server installer sets up InnoDB as

use `mysql_tzinfo_to_sql`_ to load time zone tables into the MySQL database.

This needs to be done just once for your MySQL server, not per database.

.. _mysql_tzinfo_to_sql: http://dev.mysql.com/doc/refman/5.5/en/mysql-tzinfo-to-sql.html

.. _mysql_tzinfo_to_sql: http://dev.mysql.com/doc/refman/5.6/en/mysql-tzinfo-to-sql.html

Creating your database

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

This ensures all tables and columns will use UTF-8 by default.

.. _create your database: http://dev.mysql.com/doc/refman/5.0/en/create-database.html

.. _create your database: http://dev.mysql.com/doc/refman/5.6/en/create-database.html

.. _mysql-collation:

manipulating the database tables; Django doesn't provide a way to set this on

the model definition.

.. _documented thoroughly: http://dev.mysql.com/doc/refman/5.0/en/charset.html

.. _documented thoroughly: http://dev.mysql.com/doc/refman/5.6/en/charset.html

By default, with a UTF-8 database, MySQL will use the

``utf8_general_ci`` collation. This results in all string equality

``init_command``, and ``sql_mode``. Consult the `MySQLdb documentation`_ for

more details.

.. _MySQL option file: http://dev.mysql.com/doc/refman/5.0/en/option-files.html

.. _MySQL option file: http://dev.mysql.com/doc/refman/5.6/en/option-files.html

.. _MySQLdb documentation: http://mysql-python.sourceforge.net/

Creating your tables

    .. _pytz: http://pytz.sourceforge.net/

    .. _Time Zones: http://www.postgresql.org/docs/current/static/datatype-datetime.html#DATATYPE-TIMEZONES

    .. _Choosing a Time Zone File: http://docs.oracle.com/cd/B19306_01/server.102/b14225/ch4datetime.htm#i1006667

    .. _mysql_tzinfo_to_sql: http://dev.mysql.com/doc/refman/5.5/en/mysql-tzinfo-to-sql.html

    .. _mysql_tzinfo_to_sql: http://dev.mysql.com/doc/refman/5.6/en/mysql-tzinfo-to-sql.html

none

~~~~

database to add the full-text index. By default Django uses BOOLEAN MODE for

full text searches. See the `MySQL documentation`_ for additional details.

.. _MySQL documentation: http://dev.mysql.com/doc/refman/5.1/en/fulltext-boolean.html

.. _MySQL documentation: http://dev.mysql.com/doc/refman/5.6/en/fulltext-boolean.html

.. fieldlookup:: regex

backends.

.. _PostgreSQL: http://www.postgresql.org/docs/current/static/multibyte.html

.. _MySQL: http://dev.mysql.com/doc/refman/5.0/en/charset-database.html

.. _MySQL: http://dev.mysql.com/doc/refman/5.6/en/charset-database.html

.. setting:: TEST_COLLATION

a more restrictive encoding -- for example, latin1 (iso8859-1) -- you won't be

able to store certain characters in the database, and information will be lost.

* MySQL users, refer to the `MySQL manual`_ (section 10.1.3.2 for MySQL 5.1)

  for details on how to set or alter the database character set encoding.

* MySQL users, refer to the `MySQL manual`_ for details on how to set or alter

  the database character set encoding.

* PostgreSQL users, refer to the `PostgreSQL manual`_ (section 22.3.2 in

  PostgreSQL 9) for details on creating databases with the correct encoding.

* SQLite users, there is nothing you need to do. SQLite always uses UTF-8

  for internal encoding.

.. _MySQL manual: http://dev.mysql.com/doc/refman/5.1/en/charset-database.html

.. _MySQL manual: http://dev.mysql.com/doc/refman/5.6/en/charset-database.html

.. _PostgreSQL manual: http://www.postgresql.org/docs/current/static/multibyte.html

All of Django's database backends automatically convert Unicode strings into