diff options
| author | Ramiro Morales <cramm0@gmail.com> | 2012-02-11 18:01:53 +0000 |
|---|---|---|
| committer | Ramiro Morales <cramm0@gmail.com> | 2012-02-11 18:01:53 +0000 |
| commit | 4b81d790a83e8710032ea58a8edbc8b8dab8fbcf (patch) | |
| tree | 5bd7c386410e31daab1b4dcdefdbc7f51de9365c /docs/ref | |
| parent | d72d5ce8274992ce01e39f866a7a250bc459eefe (diff) | |
Updated SpatiaLite GeoDjango test setup instructions for version 3.0.
Also, fixed documentation typos introduced in r17496.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@17507 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs/ref')
| -rw-r--r-- | docs/ref/contrib/gis/install.txt | 2 | ||||
| -rw-r--r-- | docs/ref/contrib/gis/testing.txt | 14 |
2 files changed, 5 insertions, 11 deletions
diff --git a/docs/ref/contrib/gis/install.txt b/docs/ref/contrib/gis/install.txt index d54479b282..9d67242b2d 100644 --- a/docs/ref/contrib/gis/install.txt +++ b/docs/ref/contrib/gis/install.txt @@ -582,7 +582,7 @@ For this, a number of spatial metadata tables must be created in the database before any spatial query is performed against it. If you are using SpatiaLite 3.0 or newer then use the ``spatialite`` utility to -call the ``InitSpatiaMetaData()`` function whch will take care of that (you can +call the ``InitSpatiaMetaData()`` function which will take care of that (you can safely ignore the error messages shown) then you can skip the rest of this section:: diff --git a/docs/ref/contrib/gis/testing.txt b/docs/ref/contrib/gis/testing.txt index ffa9c94190..9270c9f7d6 100644 --- a/docs/ref/contrib/gis/testing.txt +++ b/docs/ref/contrib/gis/testing.txt @@ -114,13 +114,8 @@ spatial database entitled ``template_postgis``. SpatiaLite ========== -You will need to download the `initialization SQL`__ script for SpatiaLite:: - - $ wget http://www.gaia-gis.it/spatialite/init_spatialite-2.3.zip - $ unzip init_spatialite-2.3.zip - -If ``init_spatialite-2.3.sql`` is in the same path as your project's ``manage.py``, -then all you have to do is:: +You need to make sure needed spatial tables are created in your test spatial +database as described in :ref:`create_spatialite_db`. Then all you have to do is:: $ python manage.py test @@ -132,6 +127,8 @@ Settings ``SPATIALITE_SQL`` ^^^^^^^^^^^^^^^^^^ +(only relevant when using a SpatiaLite version older than 3.0). + By default, the GeoDjango test runner looks for the SpatiaLite SQL in the same directory where it was invoked (by default the same directory where ``manage.py`` is located). If you want to use a different location, then @@ -139,9 +136,6 @@ you may add the following to your settings:: SPATIALITE_SQL='/path/to/init_spatialite-2.3.sql' -__ http://www.gaia-gis.it/spatialite/init_spatialite-2.3.zip - - .. _geodjango-tests: GeoDjango Tests |