Ran 'CREATE EXTENSION postgis' during prepare_database hook

DatabaseWrapper.prepare_database has been introduced in 307de67073.

2 files changed, 10 insertions, 0 deletions

diff --git a/docs/ref/contrib/gis/install/postgis.txt b/docs/ref/contrib/gis/install/postgis.txt
index e9c611aa31..ab7da31861 100644
--- a/docs/ref/contrib/gis/install/postgis.txt
+++ b/docs/ref/contrib/gis/install/postgis.txt
@@ -68,6 +68,12 @@ spatial functionality::
 No PostGIS topology functionalities are yet available from GeoDjango, so the
 creation of the ``postgis_topology`` extension is entirely optional.
 
+.. versionchanged:: 1.8
+
+    The ``CREATE EXTENSION postgis`` command is now automatically run during
+    the :djadmin:`migrate` process. You can still create it manually if you
+    wish.
+
 .. _spatialdb_template_earlier:
 
 Creating a spatial database template for earlier versions
diff --git a/docs/releases/1.8.txt b/docs/releases/1.8.txt
index 2ddcaf25bb..a233edd443 100644
--- a/docs/releases/1.8.txt
+++ b/docs/releases/1.8.txt
@@ -135,6 +135,10 @@ Minor features
 * The Spatialite backend now supports ``Collect`` and ``Extent`` aggregates
   when the database version is 3.0 or later.
 
+* The PostGIS 2 ``CREATE EXTENSION postgis`` and the Spatialite
+  ``SELECT InitSpatialMetaData`` initialization commands are now automatically
+  run by :djadmin:`migrate`.
+
 * Compatibility shims for ``SpatialRefSys`` and ``GeometryColumns`` changed in
   Django 1.2 have been removed.