#28077: Allow specifying custom operator classes for PostgreSQL indexes
-------------------------------------+-------------------------------------
Reporter: IzyJeepee | Owner: Ian Foote
Type: New feature | Status: assigned
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Normal | Resolution:
Keywords: postgres, gin, | Triage Stage: Accepted
operator, class |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Ian Foote):
I've noticed that in the
[https://github.com/django/django/blob/master/django/contrib/gis/db/backends/postgis/schema.py#L23-L41
postgis schema editor], we have custom index creation code for single-
field indexes for {{{geodetic}}} fields. For example, we set the
{{{GIST_GEOMETRY_OPS_ND}}} operator class for fields with dimension higher
than two.
It would probably be good to refactor to allow this custom code to
integrate with the operator class support I've added, but I'm not familiar
enough with postgis to be confident making a change without guidance.
--
Ticket URL: <https://code.djangoproject.com/ticket/28077#comment:8>
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.9916124b0a4dd13157e2a2cfeba3db93%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
