You look like the only person that can answer this question:

Situation:
Links SQL, Under mod_perl and Apache:DBI

Problem:
When changing the indexing method in Links Properties i experience erratic behavior in search results in the first 3/4 tries, after that everything get's fixed.

If I use MYSQL indexing method there's NO WAY I get results. I KNOW MYSQL rules for full text indexing, i'm not searching for words repeated in all other records i'm searching for UNIQUE words only found in one record, I tried re-indexing, repairing search to no avail. there's NO way I can get results under mod_perl for the MYSQL indexing method.

Aww you are having bad luck - Alex is away

What do you mean by "erratic"?


I certianly recommed INTERNAL indexing for best results - mysql indexing is poor and gives bad results.

You're probably right about alex being your best hope <G> He's really into mod_perl.

What do you mean "the first few tries" ? Just your first search? Or with any keyword at any time?

If it's just at first, it's probably the server catching up to the changes. mod_perl caches a lot of stuff, and that would include the code for accessing the database. Until that recycles, you might get erratic results.

Did you try restarting the whole server?


PUGDOG� Enterprises, Inc.

The best way to contact me is to NOT use Email.
Please leave a PM here.

erratic means:

shows HTML (in text style)
sometimes gives results, some times not. and this is only if I change the indexing method.

Regarding the MYSQL index I have a question:

For a Million record DB, will Internal work as well as the MYSQL indexing Method? why does the GForum uses the MYSQL method then?

I'm not sure about showing html as text but definitely drop mysql indexing for internal. The indexing in mysql4 is supposedly vastly improved but if you are using mysql3 then definitely use internal. Internal will work fine for large databases, the only draw back is the need to run nph-index.cgi which can take a few hours on a large database.

I think I know the reason why i'm not seeing results when using the MySQL indexing method.

The Description field in my Links DB was a TEXT, Regular INDEXED field of size 255 , a long time ago I dumped the DB schemas to import them in my local machine and I received an error about the description field being incorrect or something like that, so I changed it to VARCHAR 255 and indexed it. I've running like this a long time now.

The problem I have, is that no matter what I do i can NOT set the field back to text and REGULAR index because it says TEXT field can not be indexed.. go figure, what i'm doing wrong??

A couple of things, the MYSQL search driver is a little finnicky when dealing with mysql 3. We've got a new driver for MYSQL 4 that works a little better. What may be happening is that for mysql fulltext indexing, if the keyword being searched occurs in more than half of the records, it will be silently dropped. Depending on how what portion of the search is affected, the search driver may return the correct records, all records or no records on occasion.

What's the exact error you're seeing when you try to change the field? One thing that may work if you're simply trying to change the field is to do it manually (using something like mysqlman or mysqlcc) then resync the def files.

Interesting, I just upgraded the MySQL instalation to version 4.0.12 and all my indexing problems dissapeared. Now Indexing with the MYSQL method works as it should. Aki, what driver is the one that you mention? a new SQL.pm? can I get it?

I agree with PugDog... I know when I changed my indexing method under mod_perl, the web server had to be restarted. When using mod_perl, it loads the perl interpreters, perl modules, etc. into memory. When making changes to indexing methods, weights, etc., it's a good idea to restart the web server for the changes to take effect. Otherwise, you can get very strange results (things work sometimes and sometimes they don't as if they were cached).

Sean