#24672 closed Cleanup/optimization (fixed)
Remove postgis_topology creation from PostGIS install page
Reported by: | Serhiy | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | yes | UI/UX: | no |
Description
Why include "CREATE EXTENSION postgis_topology;" in https://docs.djangoproject.com/en/dev/ref/contrib/gis/install/postgis/ if it's useless for Django anyway?
Change History (8)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
Unnecessary action that takes time and causes confusion.
It's so obvious to me that I can't even find the words to explain it. Why would you need a useless action in a tutorial? Adding the note _afterwards_ just causes a "what." reaction.
comment:3 by , 10 years ago
Type: | Uncategorized → Cleanup/optimization |
---|
comment:4 by , 10 years ago
What about this:
-
docs/ref/contrib/gis/install/postgis.txt
diff --git a/docs/ref/contrib/gis/install/postgis.txt b/docs/ref/contrib/gis/install/postgis.txt index 74c688f..c31ac71 100644
a b spatial functionality:: 63 63 $ createdb <db name> 64 64 $ psql <db name> 65 65 > CREATE EXTENSION postgis; 66 > CREATE EXTENSION postgis_topology;67 66 68 No PostGIS topology functionalities are yet available from GeoDjango, so the 69 creation of the ``postgis_topology`` extension is entirely optional. 67 GeoDjango itself does currently not leverage any of the `PostGIS topology 68 functionalities`__, but if you plan to use them at some point you can also 69 install the ``postgis_topology`` extension by issuing ``CREATE EXTENSION 70 postgis_topology;``. 71 72 __ http://postgis.net/docs/Topology.html 70 73 71 74 .. versionchanged:: 1.8 72 75
comment:6 by , 10 years ago
Triage Stage: | Unreviewed → Ready for checkin |
---|
Suggestion to simplify the wording a bit: "GeoDjango does not currently leverage any PostGIS topology functionality. If you plan to use those features at some point, you can also ..."
Discussion here. I don't know if Django might add some features for it in the future, but does the current note cause any harm?