Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

TeeJay (2309)

TeeJay
  (email not shown publicly)
http://www.aarontrevena.co.uk/

Working in Truro
Graduate with BSc (Hons) in Computer Systems and Networks
pm : london.pm, bath.pm, devoncornwall.pm
lug : Devon & Cornwall LUG
CPAN : TEEJAY [cpan.org]
irc : TeeJay
skype : hashbangperl
livejournal : hashbangperl [livejournal.com]
flickr :hashbangperl [flickr.com]

Journal of TeeJay (2309)

Wednesday November 13, 2002
11:09 AM

mysql 4 strange behaviour

[ #8932 ]
I found some strange behaviour in MySQL 4.04 installed on $bigproject development and production servers.

Full text BOOLEAN MODE queries seemed to stop working, the same query against the same records stopped returning any results.

It seems that changing the data structure of the tables affected the fulltext indexing in an odd way - the changes added new columns that weren't fulltext indexed or anything and so shouldn't have even required index regeneration.

My first approach was to rebuild the tables with the new data structure. This didn't fix it.

The next thing I tried was rewriting the SQL Query, eventually I added a match() against() > 0 condition and suddenly everything worked again. It seems the match/against condition was returning a non-true value when boolean mode was used but was greater than 0. Very very odd.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.