Re: temp workaround for fulltext 50% occurence threshold

2001-12-20 Thread Mark Maunder
Sergei Golubchik wrote: > > > > Hmm, them 4.0.1 (with IN BOOLEAN MODE) won't help either :-( > > > It uses the same scoring scheme as the above query in 4.0.0 > > > > Where can I get 4.0.1? I dont see it on the website. > > Because it's not officially out yet :-) > (you can always use it before "

Re: temp workaround for fulltext 50% occurence threshold

2001-12-20 Thread Sergei Golubchik
Hi! On Dec 20, Mark Maunder wrote: > Sergei Golubchik wrote: > > I'm using version 4. > > I tried using 'IN BOOLEAN MODE' under version 4.0.0 but it doesn't recognize > it. I'm using the MySQL 4.0.0-alpha Server (i386) (6.2M) binary RPM. > > Should I compile from source? I would like to but a

Re: temp workaround for fulltext 50% occurence threshold

2001-12-20 Thread Mark Maunder
Sergei Golubchik wrote: > Mark, it's no point in discussing how things could be > done in 3.23 branch - nothing can be changed there, > this is exactly the reason we call it "stable". > > How to get rid of 50% threshold is explained in the manual - > for MySQL-3.23.x the only way is to modify the

Re: temp workaround for fulltext 50% occurence threshold

2001-12-20 Thread Sergei Golubchik
Hi! On Dec 20, Mark Maunder wrote: > > I agree with your logic of words that occur more frequently have a > lesser weight - it makes alot of natural language sense. But there > should be a way to either disable the '50% occurence = zero weight' > setting or perhaps disable word weighting altoget