#23423: Integrate unaccent lookups in django.contrib.postgres
----------------------------------+--------------------------------------
Reporter: tchaumeny | Owner:
Type: New feature | Status: new
Component: contrib.postgres | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Comment (by tchaumeny):
I should mention that I'm not quite satisfied with the implementation in
the commit above. The current lookup API in Django does not allow for real
accent insensitive lookup. More generally, it does not allow for any *SQL
transformation*-insensitive search as the transformation is only applied
to the left-hand side of the lookup, never to the right side.
I discussed that with akaariai and made a proposition for bilateral
transformations, which is tracked in #23493, which I believe is a
prerequisite for implementing robust accent-insensitive lookups in Django.
--
Ticket URL: <https://code.djangoproject.com/ticket/23423#comment:3>
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.72558ade24579046a07386d88dc6c15a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
