Browse files

Updated SpatiaLite GeoDjango test setup instructions for version 3.0.

Also, fixed documentation typos introduced in r17496.

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent d72d5ce commit 4b81d790a83e8710032ea58a8edbc8b8dab8fbcf @ramiro ramiro committed Feb 11, 2012
@@ -103,7 +103,7 @@ def load_spatialite_sql(self):
This routine loads up the SpatiaLite SQL file.
if self.connection.ops.spatial_version[:2] >= (3, 0):
- # Spatialite >= 3.0.x -- No ned to load any SQL file, calling
+ # Spatialite >= 3.0.x -- No need to load any SQL file, calling
# InitSpatialMetaData() transparently creates the spatial metadata
# tables
cur = self.connection._cursor()
@@ -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
@@ -114,13 +114,8 @@ spatial database entitled ``template_postgis``.
-You will need to download the `initialization SQL`__ script for SpatiaLite::
- $ wget
- $ unzip
-If ``init_spatialite-2.3.sql`` is in the same path as your project's ````,
-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 test
@@ -132,16 +127,15 @@ Settings
+(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
```` is located). If you want to use a different location, then
you may add the following to your settings::
.. _geodjango-tests:
GeoDjango Tests

0 comments on commit 4b81d79

Please sign in to comment.