Changes between Initial Version and Version 1 of Ticket #23423, comment 3


Ignore:
Timestamp:
09/28/2014 01:35:00 PM (6 years ago)
Author:
Thomas Chaumeny
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #23423, comment 3

    initial v1  
    11I 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.
    22
    3 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.
     3I discussed that with akaariai and made a proposition for bilateral transformations - tracked in #23493 - which I believe is a prerequisite for implementing robust accent-insensitive lookups in Django.
Back to Top