bulk at thecodecave.com
Sat Dec 4 17:53:07 UTC 2010
Agreed. Your method for conversion should work fine if you drop the
full text searches first. There are various trade-offs between InnoDB
and MyISAM. You need to choose the one that meets your requirement best.
I can confirm that you convert MU installs with hundreds of blogs
without a problem. Just make sure you watch your resources while you
are doing it. Running both InnoDB and MyISAM database engines will
obviously take up more memory, but that's easy to forget. You're using
two sets of buffers and logs et al. So when you switch over, you may
want to switch all databases over.
On 12/4/2010 4:14 AM, Ozh wrote:
> AFAIK, WP doesn't create FULLTEXT indexes. These have probably been
> created by a plugin.
> On Sat, Dec 4, 2010 at 5:33 AM, Yang Zhang<yanghatespam at gmail.com> wrote:
>> Can WordPress use InnoDB? If so, how do I tell WordPress to use
>> InnoDB? If I have an existing database, how do I migrate it to InnoDB?
>> I tried simply mysqldump-ing and loading back the tables but with
>> ENGINE=innodb instead of ENGINE=myisam, but that failed because
>> FULLTEXT indexes are not supported by innodb. Thanks in advance.
More information about the wp-hackers