#33294: opclasses missing in PostGIS's 3D geometry indexes
---------------------------------+--------------------------------------
Reporter: Tim Graham | Owner: nobody
Type: Bug | Status: closed
Component: GIS | Version: 4.0
Severity: Release blocker | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => needsinfo
Comment:
Thanks for the report, however it creates exactly the same set of indexes
for me 🤔 (see attachments) and it's covered by
[https://github.com/django/django/blob/12fe3224f5086161462faf614cad91f3fad32e78/tests/gis_tests/gis_migrations/test_operations.py#L197-L218
test_add_3d_field_opclass()]. Maybe it's reproducible on a 3rd-party
backend.
--
Ticket URL: <https://code.djangoproject.com/ticket/33294#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.a219bb254b8286e094d7f064240b2755%40djangoproject.com.
