Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Mixed database table types (MyISAM vs InnoDB)

    WordPress (Developer)
    2
    4
    26
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • d19dotca
      d19dotca last edited by

      Hello. I noticed in looking at the databases of various websites (trying to cleanup some old plugin data) that I have a mixture of MyISAM and InnoDB table types. Some are MyISAM type and some are InnoDB type.

      I assume they should all be InnoDB as I tried deploying a fresh instance of WordPress and used PHPMyAdmin to verify that they are all InnoDB by default, so I am presuming I should be converting the MyISAM to InnoDB.

      Any thoughts on how to fix this all to InnoDB? Is this something I should just ignore? My concern is this may be an issue down the road and so if I can be proactive then I'd rather be proactive.

      Screenshots below...

      Older install (notice the mix of InnoDB and MyISAM types):
      f8b336c6-d705-4fb6-9e55-6db1a214ff61-image.png

      Fresh install (notice the InnoDB is the type used for all tables):
      259e31bd-d8a3-414b-b760-f1787193659b-image.png

      --
      Dustin Dauncey
      www.d19.ca

      girish 1 Reply Last reply Reply Quote 0
      • girish
        girish Staff @d19dotca last edited by

        @d19dotca said in Mixed database table types (MyISAM vs InnoDB):

        MyISAM

        afaik, MyISAM is sort of obsolete. We only support InnoDB since the beginning. Was the initial WP installation from Cloudron ?

        TBH, I didn't even know one could mix tables this way!

        1 Reply Last reply Reply Quote 0
        • girish
          girish Staff last edited by

          According to internet, you can do ALTER TABLE tablename ENGINE=InnoDB; to convert. I would suggest converting. Atleast, all our tests in the MySQL addon assume InnoDB and never tested with MyISAM.

          d19dotca 1 Reply Last reply Reply Quote 1
          • d19dotca
            d19dotca @girish last edited by

            @girish okay I’ll try that, thanks for looking into it Girish! It’s definitely odd and I’m surprised I only recently discovered this concern. Some of them definitely existed before Cloudron days and came over as part of the “all in one migration” plugin which I have a feeling overwrite the database to match the original source, so likely is part of the reason there. Some newer ones also have it though but thinking further I think it’s because it was an issue in the template one I spun up new site builds from.

            I’ll try converting and hopefully that’ll help with some stuff. Will report back on whether it’s successful or not 🙂

            --
            Dustin Dauncey
            www.d19.ca

            1 Reply Last reply Reply Quote 1
            • First post
              Last post
            Powered by NodeBB