[wp-hackers] Lost categories upgrading to 2.5.1
intoxination at gmail.com
Thu May 1 17:23:24 GMT 2008
InnoDB needs to be left up to the user. MySQL doesn't configure InnoDB
by default, so chances are it will break for a bunch of people. As far
as using InnoDB - it rocks on a table that gets updated a lot. On a
couple of our sites that see an average of 2,000 comments a day,
changing wp_comments and wp_posts to InnoDB was a life saver.
> On Thu, May 1, 2008 at 5:21 AM, Sabin Iacob <iacobs at m0n5t3r.info> wrote:
> > perhaps because mysql won't give you transactions by default? this could
> > be, of course, solved by making the tables InnoDB when initially installing,
> > provided the host has it configured (the read performance - which is what
> > matters for a blog/CMS - should be about the same for InnoDB and MyISAM, but
> > I have yet to see a comparison between the two using Wordpress).
> Ahh. Didn't know that. Did some research and yeah, transactions are
> not supported properly on MyISAM tables, which kinda blows IMO.
> Of course, the next upgrade could also have "ALTER TABLE whatever
> ENGINE = InnoDB" in it...
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers