#33373: Support expressions on rhs for __has_keys, __has_any_keys JSONField
lookups.
-------------------------------------+-------------------------------------
Reporter: john-parton | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | 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
-------------------------------------+-------------------------------------
Comment (by john-parton):
Thanks for the feedback.
Examples in documentation aren't necessarily meant to be exhaustive.
Obviously it's impractical to give an example for every way a feature can
be use.
I do think it's a violation of expectations.
At the very least, I think it would be helpful to update the documentation
so that it notes that only iterables of strings are valid values for that
transformation.
It sounds like the ?& operator only works on Postgres, and not Oracle or
other database backends. Is that right?
Are we amenable to making it work with the Postgres backend, and
continuing to produce the current error for the other backends?
--
Ticket URL: <https://code.djangoproject.com/ticket/33373#comment:2>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/069.337ef47a19b1d013db127ef901ec0f6c%40djangoproject.com.
