#16455: Postgis 2.0 Compatibility
---------------------------------------+-----------------------------
Reporter: ckarrie | Owner: nobody
Type: New feature | Status: new
Milestone: 1.4 | Component: GIS
Version: 1.3-beta | Severity: Normal
Resolution: | Keywords: postgis 2.0
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
---------------------------------------+-----------------------------
Changes (by ckarrie):
* keywords: => postgis 2.0
Comment:
I discovered that Django doesn't create the '''indexes''' as well as the
'''geometry columns'''.
My workaround "by hand":
{{{
SELECT
AddGeometryColumn('public','bzs_analyze_undevpotential','the_geom',21781,'MULTIPOLYGON',2);
CREATE INDEX bzs_analyze_undevpotential_the_geom
ON bzs_analyze_undevpotential
USING GIST ( the_geom );
}}}
then
{{{
VACUUM ANALYZE bzs_analyze_undevpotential;
}}}
works perfect so far.
It seems, that the geometry colums can be added with the
AddGeometryColumn-Function and with following SQL-Statement:
{{{
CREATE TABLE bzs_analyze_undevpotential
(
[...]
the_geom geometry(MultiPolygon,21781),
[...]
);
}}}
I hope that helps!
--
Ticket URL: <https://code.djangoproject.com/ticket/16455#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
