#27824: Cannot chain unaccent transform with key lookup in Postgres JSON field
-------------------------------------+-------------------------------------
Reporter: Aymeric Augustin | Owner: Simon
| Charette
Type: New feature | Status: assigned
Component: contrib.postgres | Version: 1.10
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
I'm afraid we'll have to make this a ''wontfix'' as exposing a new lookup
would break backward compatiblity for existing users of `JSONField` who
have data containing a key named `unaccent`.
#27257 didn't register any new lookups, it only made existing text lookups
that were available since the introduction of `JSONField` use `->>`
instead of `(lhs -> key)::text`.
This could also be closed as duplicate of #26511 which proposes to
document `KeyTextTransform` as a public API so you could use
`KeyTextTransform('first_name', F('inputs'))` instead of the `RawSQL`
workaround you are using right now.
--
Ticket URL: <https://code.djangoproject.com/ticket/27824#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.42a2e3561546adfddb8a15b4e68ebbf5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
