Answers.Body: <p>Yes, you can change the engine but they are temporary tables so will disappear soon - and more will appear.  </p>
  
  <p>It is a warning rather than an error.  The data integrity message is intended to relate to the permanent tables, not these temporary ones. Since your permanent tables show as InnoDB you can safely ignore this message.</p>
  
  <p>I've logged this here: <a href="https://lab.civicrm.org/dev/core/issues/591" rel="nofollow noreferrer">https://lab.civicrm.org/dev/core/issues/591</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-12-13T10:05:14.373Z
Answers.Text: The fix for this has gone into 5.8.1
Answers.UserDisplayName: Aidan
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-12-12T17:05:49.087Z
Answers.LastActivityDate: 2018-12-12T17:05:49.087Z
Answers.UserDisplayName: Aidan
Answers.Body: <p>You could adjust to remove error, but these tmp tables will always by MyIsam, every time they are created. </p>
  
  <p>I am not sure if setting the default storage engine as InnoDB is okay.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-12-12T16:49:24.857Z
Answers.LastActivityDate: 2018-12-12T16:49:24.857Z
Answers.UserDisplayName: Andy Burns
Answers.Body: <p>We've been seeing this in Drupal installs as well (with CiviCRM 5.6.1) so this isn't a brand new issue.  (Also - welcome to Civi SE, Stefan!  We're glad you're here.)</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-12-12T20:25:40.193Z
Answers.LastActivityDate: 2018-12-12T20:25:40.193Z
Answers.UserDisplayName: Lesley Carter - BackOffice
Body: <p>After update to Civicrm 5.8.0 I got a:</p>
  
  <pre><code>MyISAM Database Engine
  Your database is configured to use the MyISAM database engine. CiviCRM requires InnoDB. You will need to convert any MyISAM tables in your database to InnoDB. Using MyISAM tables will result in data integrity issues.
  </code></pre>
  
  <p>Had a look into the db, found out it's just about three tables:
  <a href="https://i.sstatic.net/N10jO.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/N10jO.png" alt="enter image description here"></a></p>
  
  <p>Is it save to do <code>ALTER TABLE tablename ENGINE=InnoDB;</code>?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-12-12T22:40:39.587Z
Comments.Text: Temp tables should be generating warnings: See https://lab.civicrm.org/dev/core/issues/462 where this was fixed.  While you can change the database engine safely, this should (and will) get fixed in the core product so it doesn't generate this warning.
Comments.UserDisplayName: Jon G - Megaphone Tech
Tags: <wordpress><database>
Title: Wordpress: MyISAM Database Engine Error after update
ThreadText: # Wordpress: MyISAM Database Engine Error after update
  
  (Asked by: username_0 on 2018-12-12)
  
  After update to Civicrm 5.8.0 I got a:
  MyISAM Database Engine
  Your database is configured to use the MyISAM database engine. CiviCRM requires InnoDB. You will need to convert any MyISAM tables in your database to InnoDB. Using MyISAM tables will result in data integrity issues.
  
  Had a look into the db, found out it's just about three tables:
  
  Is it save to do ALTER TABLE tablename ENGINE=InnoDB;?
  
  **Tags:** wordpress, database
  
  > **Comments:**
  > **username_1**: Temp tables should be generating warnings: See https://lab.civicrm.org/dev/core/issues/462 where this was fixed.  While you can change the database engine safely, this should (and will) get fixed in the core product so it doesn't generate this warning.  
  
  ---
  
  ## 3 answers
  
  ### Answer by username_2 on 2018-12-12. Score: 2
  
  Yes, you can change the engine but they are temporary tables so will disappear soon - and more will appear.
  
  It is a warning rather than an error. The data integrity message is intended to relate to the permanent tables, not these temporary ones. Since your permanent tables show as InnoDB you can safely ignore this message.
  
  I've logged this here: <https://lab.civicrm.org/dev/core/issues/591>
  
  > **Comments:**
  > **username_2**: The fix for this has gone into 5.8.1  
  
  ---
  
  ### Answer by username_3 on 2018-12-12. Score: 0
  
  You could adjust to remove error, but these tmp tables will always by MyIsam, every time they are created.
  
  I am not sure if setting the default storage engine as InnoDB is okay.
  
  
  ---
  
  ### Answer by username_4 on 2018-12-12. Score: 0
  
  We've been seeing this in Drupal installs as well (with CiviCRM 5.6.1) so this isn't a brand new issue. (Also - welcome to Civi SE, username_0! We're glad you're here.)
  
  
  ---
  
  