Support » Plugin: Optimize Database after Deleting Revisions » Why does the plugin add it’s own table using MyIsam?

  • Resolved gecko_guy

    (@gecko_guy)


    Hi,

    Love this plugin, always have, but something which I’ve only just noticed for the first time in all the years I’ve been using it, is that if the rest of the DB uses InnoDB, ODB adds its own table for the logs using MyISAM.

    Can you explain the reasons for this please? MyISAM is scheduled for decommissioning when MySQL 8.0 is released.

    I do understand that MyISAM is required for backward compatibility with really old sites, but the time is coming when MyISAM will be removed completely, in which case there may be conflicts..

    I guess I’m more curious than anything else (and I haven’t used MyISAM for many years either so not sure how I never noticed this before).

Viewing 1 replies (of 1 total)
  • Plugin Author cageehv

    (@cageehv)

    Hey gecko_guy,

    I like the MyISAM engine more than the InnoDB engine (just a personal preference).
    But, you are right: MyISAM will disappear.

    I removed the MyISAM engine for the ODB log table, so it will use the MySQL ‘default-storage-engine’.

    It will be included in v4.6.3 of the plugin (not sure yet, when it will be released).

    Thanks for your feedback!

    peace,
    Rolf

Viewing 1 replies (of 1 total)
  • The topic ‘Why does the plugin add it’s own table using MyIsam?’ is closed to new replies.