#23636: GeoDjango is creating two indexes for geometry field
-------------------------------------+-------------------------------------
Reporter: george-silva | Owner: nobody
Type: Bug | Status: closed
Component: GIS | Version: 1.7
Severity: Normal | Resolution: wontfix
Keywords: geodjango, index, | Triage Stage:
spatial | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by claudep):
* status: new => closed
* needs_better_patch: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_docs: => 0
Comment:
As you discovered, the immediate solution is to use `spatial_index`
instead of `db_index`.
You are right in that the current state of index creation/management is a
bit blurry now, but "we have a plan™"! See
https://github.com/django/deps/pull/6/files
Hopefully this planned refactoring of indexes will solve this issue. I
don't think it's worth keeping the ticket open. Thanks for the detailed
report anyway.
--
Ticket URL: <https://code.djangoproject.com/ticket/23636#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/070.3bb696673638e75ffe84e71a2c746989%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
