Changes between Initial Version and Version 1 of Ticket #23423


Ignore:
Timestamp:
09/06/2014 09:21:31 AM (6 years ago)
Author:
Thomas Chaumeny
Comment:

I tried something using Tranform, as it looks like it was made for that kind of things: https://github.com/tchaumeny/django/commit/cb3d7808c20094636bacb0576bc738ee466d256a

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #23423

    • Property Has patch set
  • Ticket #23423 – Description

    initial v1  
    1 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 are not very clean (and do not make use of the new API).
    2 
    3 The way I see it, `unaccent` would be a sub-application within `django.contrib.postgres` which should be enabled for the lookups to be active (that requires postgres >= 9.0).
     1After 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).
Back to Top