Might just want to add something like this to the SQL incase the table is set to use something other than the MyISAM storage engine;

ALTER TABLE 'node_revisions' ENGINE = MYISAM

Comments

brashquido’s picture

brashquido commented

Just to expand on this. As of Drupal 4.7 all tables for the core will be engine agnostic, meaning that the storage engine type will be set to whatever the server default is. In my case this was InnoDB, and I needed to set the storage engine type to MyISAM as InnoDB does not support indexing.

Another thing is as the node_revision table is probably going to be the busiest table in any Drupal install (it contains the teaser and body fields for every node), it is likely that even just mederately busy sites would benefit from using the InnoDB storage engine type. Is there any possibility of developing Similar Entries further so that it can support the InnoDB storage engine as well?

deekayen’s picture

deekayen commented

Right now, I'm going to label this a documentation issue. InnoDB Fulltext support was in progress and targeted for release this year before they were bought: http://72.14.203.104/search?q=cache:OmgBGm6nMA0J:www.innodb.com/todo.php...

I don't know if that has changed or not. Quite frankly, I'm still using MyISAM, so I don't have much interest in implementing an alternative. Does InnoDB have a different text index I'm not aware of? I think figuring out a LIKE hack would be too ugly to implement.

deekayen’s picture

deekayen commented
Status: Active » Fixed

Ok, I committed some extra docs to readme and the alter statement to the install file. If you really have an idea how the InnoDB thing might work, open a new issue.

brashquido’s picture

brashquido commented

No worries. I'd doubt I'll be having contention issues by using MyISAM anytime soon (12~18 months), so if fulltext indexing is still on the cards for the InnoDB storage engine then I don't see there being any reason to try tackling it now. I just didn't want to be put in a position where I start using a really useful module like this, then have to drop it from my site when they (hopefully) start generating some more serious traffic forcing the InnoDB card on me.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)