#35136: Interoperability with intarray PostgreSQL extension
-------------------------------------+-------------------------------------
Reporter: Jan Hamal Dvořák | Owner: (none)
Type: New feature | Status: closed
Component: contrib.postgres | Version: dev
Severity: Normal | Resolution: wontfix
Keywords: postgresql, | Triage Stage:
intarray | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* status: new => closed
* resolution: => wontfix
Comment:
Thank you for your report.
I don't think that Django can commit to producing SQL that is compatible
with all the combination of usage of Postgres extensions out there.
Since it allows for [https://docs.djangoproject.com/en/5.0/howto/custom-
lookups/ any lookups to be overridden] it should be trivial to write your
own subclass of `ArrayContains` and friends and register them on
`ArrayField`.
{{{#!python
from django.contrib.postgres.fields.array import ArrayContains
class ArrayContainsOperator(ArrayContains):
postgres_operator = "OPERATOR(pg_catalog.@>)"
ArrayField.register_lookup(ArrayField.register_lookup)
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35136#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/0107018d3983dfa2-999bcda5-ba94-4dc5-a3fe-8892bd8dbf66-000000%40eu-central-1.amazonses.com.
