mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-08-04 10:59:45 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

Remove no-longer-valid references to the DATABASE_* settings, the legacy code for them was already removed.

Browse source 
git-svn-id: http://code.djangoproject.com/svn/django/trunk@16733 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Alex Gaynor 2011-09-09 17:14:47 +00:00
parent 4584069c8a
commit d036b87126
4 changed files with 2 additions and 137 deletions
Download patch file Download diff file Expand all files Collapse all files

24
docs/ref/contrib/gis/db-api.txt
View file

@ -23,30 +23,6 @@ its functionality into full-fledged spatial database backends:
* :mod:`django.contrib.gis.db.backends.oracle`
* :mod:`django.contrib.gis.db.backends.spatialite`
Database Settings Backwards-Compatibility
-----------------------------------------
In :doc:`Django 1.2 </releases/1.2>`, the way
to :ref:`specify databases <specifying-databases>` in your settings was changed.
The old database settings format (e.g., the ``DATABASE_*`` settings)
is backwards compatible with GeoDjango, and will automatically use the
appropriate spatial backend as long as :mod:`django.contrib.gis` is in
your :setting:`INSTALLED_APPS`. For example, if you have the following in
your settings::
DATABASE_ENGINE='postgresql_psycopg2'
...
INSTALLED_APPS = (
...
'django.contrib.gis',
...
)
Then, :mod:`django.contrib.gis.db.backends.postgis` is automatically used as your
spatial backend.
.. _mysql-spatial-limitations:
MySQL Spatial Limitations

2
docs/ref/contrib/gis/install.txt
View file

@ -573,7 +573,7 @@ Now, the ``spatialite`` command can be used to initialize a spatial database::
.. note::
The parameter ``geodjango.db`` is the *filename* of the SQLite database
you want to use. Use the same in the :setting:`DATABASE_NAME`
you want to use. Use the same in the :setting:`DATABASES` ``"name"`` key
inside your ``settings.py``.