Main Stories
Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Article Poll

Poll I found this article to be
Very Helpful
Helpful
Not Helpful
Not Very Helpful
[ Results | Polls ]
Comments:0 | Votes:0

Innodb and Slash

posted by Krow on 02:52 PM March 9th, 2003   Printer-friendly   Email story
I'm wondering if people are using Innodb with Slash. The big issue seems to be converting tables that have FULLTEXT on them (like stories).

Anyone know if there are any advantages to having Innodb tables?

This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login
Loading... please wait.
  • All of Slashdot, Linux.com [linux.com], Newsforge [newsforge.com], Devchannel [devchannel.org], and use.perl [perk.org] are Innobb. For search we replicate to an additional DB that uses MyISAM. This solves the problem of robots that tear apart DB's while going through search engines.
    --

    --
    You can't grep a dead tree.
    • Not use.perl [perl.org]? :P
    • Hmm, this was a good story. So, if one say only has one computer that runs a website, would it be a good idea to maybe have all the tables except the ones with Fulltext (or whatever it is called) as Innodb tables?
      --

      --
      It's either on the beat or off the beat, it's that easy.
    • But why Innodb? What's the advantage over the good ol' trusted MyISAM?

      --
      lottadot [lottadot.com]
      • Innodb is faster and if your DB does crash it restores the DB a lot faster. For small sites MyISAM is fine.
        --

        --
        You can't grep a dead tree.