Hi Sergei, More full-text questions from me since I just noticed your code and doc changes. :-)
What does this new WITH QUERY EXPANSION syntax do? More relevant results? More flexible? Faster? Is it for NLQ, boolean, or both (since both ft_[nlq | boolean]_search.c are changed)? Does it have something to do with 2 level indexes, or aren't they being used yet? Sorry for all the questions! Also noticed that ft_max_word_len_for_sort has become a constant, instead of run-time definable, and ft_query_expansion_limit "replaces" it, though they don't sound related. I'm wondering about max_..._for_sort because, at least in 4.0, I need to lower it to 10-12 to keep the temp files smaller when building the index. :-( Are the temp files going to get too big in 4.1 when I can't adjust ft_max_word_len_for_sort or is the algorithm different when indexing? If the temp files are the same size as 4.0, I wish ft_max_word_len_for_sort would be restored or I'm going to have problems. :-( Thanks for your time! Matt -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
