Changes between Initial Version and Version 2 of Ticket #15203


Ignore:
Timestamp:
Feb 1, 2011, 6:53:21 AM (14 years ago)
Author:
Ramiro Morales
Comment:

(WikiFormatted slightly description)

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #15203

    • Property Cc wkornewald@… added
  • Ticket #15203 – Description

    initial v2  
    1 When you specify a ModelAdmin search_field as exact (with "=" prefix) the user's search query is split() and then multiple ``__iexact`` filters are applied, one for each word. This behavior doesn't make sense with a CharField because we're doing an iexact match (there's no way two distinct filters can match at the same time, except if we're doing a JOIN). It should just take the whole query and match against that.
     1When you specify a ModelAdmin search_field as exact (with "=" prefix) the user's search query is split() and then multiple `__iexact` filters are applied, one for each word. This behavior doesn't make sense with a !CharField because we're doing an iexact match (there's no way two distinct filters can match at the same time, except if we're doing a JOIN). It should just take the whole query and match against that.
    22
    3 The same problem probably also affects ``__search`` queries (with an "@" prefix). The string should probably also be passed directly to the DB.
     3The same problem probably also affects `__search` queries (with an "@" prefix). The string should probably also be passed directly to the DB.
Back to Top