Uploaded image for project: 'CiviCRM'
  1. CiviCRM
  2. CRM-18006

Upgrade to 4.7 Uses Wrong DB Engine

          Details

          • Type: Bug
          • Status: Done/Fixed
          • Priority: Minor
          • Resolution: Fixed/Completed
          • Affects Version/s: 4.7.1
          • Fix Version/s: 4.7.13
          • Component/s: None
          • Labels:
          • Documentation Required?:
            None
          • Funding Source:
            Core Team Funds

            Description

            When upgrading sites to 4.7.1, it appears that the upgrader creates the civicrm_system_log table without specifying InnoDB, thus it falls back on the DB default which is often MyIASM. Then CiviCRM of course shows a warning that the table is not InnoDB.

              Attachments

                Activity

                  People

                  • Assignee:
                    yashodha Yashodha Chaku
                    Reporter:
                    hershel Hershel Robinson
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    6 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: