#36694: PostGIS backend silently ignores most Index options when targeting a
single
GeometryField (expressions, condition, include, opclasses)
-------------------------------------+-------------------------------------
Reporter: Luciano de la | Owner: (none)
Iglesia |
Type: Bug | Status: new
Component: GIS | Version: 5.2
Severity: Normal | Resolution:
Keywords: postgis index | Triage Stage: Accepted
condition include |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
A workaround in the meantime could be to use `expressions=[F("location")]`
instead of `fields=["location"]`. You might have to explicitly specify
[https://www.postgresql.org/docs/current/gist.html the proper] `opclasses`
though, that would be `point_ops` in your case.
--
Ticket URL: <https://code.djangoproject.com/ticket/36694#comment:4>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019a2ddb27a4-aab1afe1-c9c6-49cb-9507-ac1fd55de024-000000%40eu-central-1.amazonses.com.
