vBulletin v3.8.9 + MySQL v5.6 & InnoDB

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • XenonKilla
    New Member
    • May 2011
    • 26
    • 3.8.x

    vBulletin v3.8.9 + MySQL v5.6 & InnoDB

    I know that the in the past it was impossible to convert the 'post' and 'thread' tables to InnoDB without losing the full-text capabilities. But now I'm reading that the InnoDB engine in MySQL v5.6+ now supports Full-Text. So is it now possible to convert my tables from MyISAM to InnoDB and still retain full-text capabilities? Will everything still function properly or am I missing something here?
  • Paul M
    Former Lead Developer
    vB.Com & vB.Org
    • Sep 2004
    • 9886

    #2
    Yes its possible, we have in fact done it ourselves on vbulletin.org
    Baby, I was born this way

    Comment

    • XenonKilla
      New Member
      • May 2011
      • 26
      • 3.8.x

      #3
      Wow really? Are there any threads/discussions about any of this?

      Comment

      • Paul M
        Former Lead Developer
        vB.Com & vB.Org
        • Sep 2004
        • 9886

        #4
        None I know of.
        Baby, I was born this way

        Comment

        • XenonKilla
          New Member
          • May 2011
          • 26
          • 3.8.x

          #5
          Alright I'll do a little digging now that I know it's possible. Thanks for the heads up.

          Comment

          • TS | Julio
            Senior Member
            • May 2002
            • 149

            #6
            This sounds awesome, please do post your findings!
            I'll do the same if I'm successful
            Julio Franco
            TechSpot.com

            Comment

            • Paul M
              Former Lead Developer
              vB.Com & vB.Org
              • Sep 2004
              • 9886

              #7
              Aside from actually just doing it, the issue you may hit is this : http://tracker.vbulletin.com/browse/VBIII-12999

              However, if you have already switched to fulltext search before converting the tables to innodb, then you should be fine.
              Baby, I was born this way

              Comment

              • TS | Julio
                Senior Member
                • May 2002
                • 149

                #8
                Thanks for the heads up!
                Since I was on 3.8.10 beta 1 I first changed the search mode, and then converted the tables.
                It was a complete success, all tables converted ok on my testserver and full text search is working fine
                Database server is MariaDB v10.0.23
                Still not running it on the live site, might take a while (waiting on a server move first).
                Julio Franco
                TechSpot.com

                Comment

                • XenonKilla
                  New Member
                  • May 2011
                  • 26
                  • 3.8.x

                  #9
                  Once the 'post' and 'thread' tables are converted to InnoDB is it still possible to convert them back to MyISAM later on down the road?

                  Also, right now all my tables are using MyISAM (except of course MEMORY tables) so would it be beneficial for me to only convert just my 'post' and 'thread' tables to InnoDB and leave the rest as MyISAM? Or should I just convert everything to InnoDB? I run a pretty large forum and my post table currently has over 1,003,525 rows. The site runs good but I'm know that table locking on the post and thread tables is definitely killing me.

                  Comment

                  widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
                  Working...