Re^7: Does Search::InvertedIndex module live up to billing?

You are joining on respondent_id and searching on response_id so you need indexes on both of those. KEY (response_id), KEY (respondent_id)

Comment on Re^7: Does Search::InvertedIndex module live up to billing?

Replies are listed 'Best First'.
Re^8: Does Search::InvertedIndex module live up to billing? by punch_card_don (Curate) on Oct 21, 2004 at 21:31 UTC
OK - I'll try the individual indexes instead of the compound primary key, and changing order of declaration...... Of course, it take about two hours to repopulate the database, it'll be tomorrow before I have results. Thanks for the help! It really is much appreciated.	[reply]
Re^9: Does Search::InvertedIndex module live up to billing? by perrin (Chancellor) on Oct 21, 2004 at 22:26 UTC
The indexes are in addition to the primary key, not instead of it. Loading goes fastest if you write it out to a tab-delimited file and use LOAD DATA INFILE, then enable the keys. (You can either do DISABLE KEYS, load, ENABLE KEYS, or you can just wait to add the indexes with ALTER TABLE commands after the data load.)	[reply]