xb95 (xb95) wrote in lj_dev,
xb95
xb95
lj_dev

Switching to InnoDB in Daughter Sites.

Alright. I was doing a code update today for Plogs.net when I ran into some problems about being unable to allocate an itemid, which I tracked down to funky new code that uses a counter table, which tracked me back to the CVS log that mentions moving to InnoDB. Alright. So I dug out more CVS log entries and diffs about the changes to the tables themselves. Then I tracked over to MySQL's online documentation and got some info on converting tables from MYISAM to InnoDB and figured out that you theoretically just need to do:

ALTER TABLE log2 TYPE=INNODB;

But that's just theoretical. Also, some auto_increment columns need to be changed, et cetera. How did LJ do this? Is there a script somewhere that automatically does this change? bin/upgrading/update-db.pl doesn't notice the changes and doesn't suggest that I do anything, and I don't want to end up losing lots of data in this process.

Suggestions?

Also, I propose that large changes like this go into this community to keep people aware of things like this. It would have saved me a lot of time and effort. Thanks.
Subscribe
  • Post a new comment

    Error

    Anonymous comments are disabled in this journal

    switch
    default userpic

    Your reply will be screened

    Your IP address will be recorded 

    Help
  • 4 comments