#30267: GeoDjango does not create correct PostGIS index for 3D geometry fields
-------------------------------------+-------------------------------------
Reporter: Casper van der Wel | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: GIS | Version: 1.11
Severity: Normal | Resolution:
Keywords: geodjango, postgis | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* type: Uncategorized => Cleanup/optimization
Comment:
Hi Casper.
Could you take a look through the
[https://docs.djangoproject.com/en/2.2/ref/contrib/postgres/indexes
/#module-django.contrib.postgres.indexes list of Postgres indexes]? There
have been additions since 1.11. #28887, #28126, adding Gist and SP-Gist
indexes in particular.
Does using these with
[https://docs.djangoproject.com/en/2.1/ref/models/options/#django.db.models.Options.indexes
`Options.indexes`] solve you having to use raw SQL?
(I appreciate that doesn't address your point about changing the lookup.)
--
Ticket URL: <https://code.djangoproject.com/ticket/30267#comment:1>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.04498654819c2eab33ba9aecce68466d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
