Included in this documentation are some additional notes and settings\nfor PostGIS users.
\nPOSTGIS_VERSIONLink to this heading#When GeoDjango’s spatial backend initializes on PostGIS, it has to perform\nan SQL query to determine the version in order to figure out what\nfeatures are available. Advanced users wishing to prevent this additional\nquery may set the version manually using a 3-tuple of integers specifying\nthe major, minor, and micro version numbers for PostGIS. For example,\nto configure for PostGIS X.Y.Z you would use:
\nPOSTGIS_VERSION = (X, Y, Z)\nDepending on your configuration, this section describes several methods to\nconfigure a database user with sufficient privileges to run tests for\nGeoDjango applications on PostgreSQL. If your\nspatial database template\nwas created like in the instructions, then your testing database user\nonly needs to have the ability to create databases. In other configurations,\nyou may be required to use a database superuser.
\nTo make a database user with the ability to create databases, use the\nfollowing command:
\n$ createuser --createdb -R -S <user_name>\nThe -R -S flags indicate that we do not want the user to have the ability\nto create additional users (roles) or to be a superuser, respectively.
Alternatively, you may alter an existing user’s role from the SQL shell\n(assuming this is done from an existing superuser account):
\npostgres# ALTER ROLE <user_name> CREATEDB NOSUPERUSER NOCREATEROLE;\nThis may be done at the time the user is created, for example:
\n$ createuser --superuser <user_name>\nOr you may alter the user’s role from the SQL shell (assuming this\nis done from an existing superuser account):
\npostgres# ALTER ROLE <user_name> SUPERUSER;\nOn Windows platforms the pgAdmin III utility may also be used as\na simple way to add superuser privileges to your database user.
\nBy default, the PostGIS installer on Windows includes a template\nspatial database entitled template_postgis.
To have the GeoDjango tests executed when running the Django test suite with runtests.py all of the databases in the settings\nfile must be using one of the spatial database backends.
The following is an example bare-bones settings file with spatial backends\nthat can be used to run the entire Django test suite, including those\nin django.contrib.gis:
DATABASES = {\n 'default': {\n 'ENGINE': 'django.contrib.gis.db.backends.postgis',\n 'NAME': 'geodjango',\n 'USER': 'geodjango',\n },\n 'other': {\n 'ENGINE': 'django.contrib.gis.db.backends.postgis',\n 'NAME': 'other',\n 'USER': 'geodjango',\n },\n}\n\nSECRET_KEY = 'django_tests_secret_key'\nAssuming the settings above were in a postgis.py file in the same\ndirectory as runtests.py, then all Django and GeoDjango tests would\nbe performed when executing the command:
$ ./runtests.py --settings=postgis\nTo run only the GeoDjango test suite, specify gis_tests:
$ ./runtests.py --settings=postgis gis_tests\n