Mercurial > public > sg101
view custom_search/fields.py @ 1037:7e0c3cbd3cda
Fix bad select_related call.
In Django 1.8, select_related now throws an error if you give it an invalid
field. This was happening. Fix that query.
Also noticed an extra query generated in the display_post template. Fixed.
author | Brian Neal <bgneal@gmail.com> |
---|---|
date | Tue, 29 Dec 2015 22:21:42 -0600 |
parents | cf9918328c64 |
children |
line wrap: on
line source
"""Custom Haystack SearchFields.""" import haystack.fields class MaxTermSizeCharField(haystack.fields.CharField): """A CharField that discards large terms when preparing the search index. Some backends (e.g. Xapian) throw errors when terms are bigger than some limit. This field omits the terms over a limit when preparing the data for the search index. The keyword argument max_term_size sets the maximum size of a whitespace delimited word/term. Terms over this size are not indexed. The default value is 64. """ DEFAULT_MAX_TERM_SIZE = 64 def __init__(self, *args, **kwargs): self.max_term_size = kwargs.pop('max_term_size', self.DEFAULT_MAX_TERM_SIZE) super(MaxTermSizeCharField, self).__init__(*args, **kwargs) def prepare(self, obj): text = super(MaxTermSizeCharField, self).prepare(obj) if text is None or self.max_term_size is None: return text terms = (term for term in text.split() if len(term) <= self.max_term_size) return u' '.join(terms)