Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-49359

Warn regarding MyISAM usage in stable branches

    XMLWordPrintable

    Details

    • Testing Instructions:
      Hide
      1. Install a site with MySQL (if you do not already have one).
      2. Set the 'mdl_config' table's database storage engine to 'MyISAM'.
      3. Visit Site administration > Server > Environment.
      4. Change the drop down to '2.9'.
      5. Confirm there is a message under the 'Other checks' section warning you that you are not using a supported database storage engine.
      6. Repeat with MariaDB (sorry!).
      Show
      Install a site with MySQL (if you do not already have one). Set the 'mdl_config' table's database storage engine to 'MyISAM'. Visit Site administration > Server > Environment. Change the drop down to '2.9'. Confirm there is a message under the 'Other checks' section warning you that you are not using a supported database storage engine. Repeat with MariaDB (sorry!).
    • Affected Branches:
      MOODLE_27_STABLE, MOODLE_28_STABLE
    • Fixed Branches:
      MOODLE_27_STABLE, MOODLE_28_STABLE
    • Sprint:
      Team Beards Sprint 4

      Description

      MDL-46064 adds a check before you can install/upgrade if the user is using MyISAM - we should warn them in the stable branches that 2.9 will prevent users from continuing with the upgrade before they change their core code.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              markn Mark Nelson
              Reporter:
              markn Mark Nelson
              Peer reviewer:
              Simey Lameze
              Integrator:
              Dan Poltawski
              Tester:
              Rajesh Taneja
              Participants:
              Component watchers:
              Matteo Scaramuccia, Andrew Nicols, Jun Pataleta, Michael Hawkins, Shamim Rezaie, Simey Lameze
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Fix Release Date:
                11/May/15