On Mar 19, 11:41 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> On 3/19/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> > That's not what I would have expected to see. Have a look at the SQL
> > that Django is generating and see if there are any clues there. To do
> > that, make sure you have DEBUG=True in your settings file (which you
> > will have by default) and then do this:
>
> That's actually the correct behavior on MySQL -- it defaults to
> ignoring words of less than four characters in full-text searches (it
> also ignores "stop words").
>
> These are configurable in MySQL via the 'ft_min_word_len' and
> 'ft_stopword_file' options.
hmm, I see, thanks. setting 'ft_min_word_len=2 solved it.
still pretty annoying. could django take care of changing this
setting?
(assuming that this is not how __search is supposed to work).
thanks
-abe
>
> --
> "Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
