Opened 10 years ago
Last modified 6 years ago
#23423 closed New feature
Integrate unaccent lookups in django.contrib.postgres — at Version 1
Reported by: | Thomas C | Owned by: | |
---|---|---|---|
Component: | contrib.postgres | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | yes | Needs documentation: | yes |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description (last modified by )
After the introduction of the Lookup
API in Django 1.7, I believe that django.contrib.postgres
could benefit from some custom lookups based on the unaccent extension of PostgreSQL (see http://www.postgresql.org/docs/9.3/static/unaccent.html). That kind of feature would be very helpful for a lot of people in latin countries, and the existing solutions seems not very clean (and do not make use of the new API).
Note:
See TracTickets
for help on using tickets.
I tried something using
Tranform
, as it looks like it was made for that kind of things: https://github.com/tchaumeny/django/commit/cb3d7808c20094636bacb0576bc738ee466d256a