Answers.Body: <p>Craft currently won't operate properly if you have GTID enabled because GTID enforces that every table involved in a SQL statements in one transaction have to utilize the same storage engine.</p>
  
  <p>While virtually all of Craft's tables use InnoDB as the storage engine, the <code>craft_searchindex</code> table is still on MyISAM, because InnoDB didn't add full-text support until MySQL 5.6 and Craft still supports back to MySQL 5.1.</p>
  
  <p>If you're running MySQL 5.6+ (which you should be because I don't believe GTID was introduced until 5.6), then you can manually change the storage engine of the <code>craft_searchindex</code> table from MyISAM to InnoDB and you shouldn't run into any issues.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-08-01T21:00:02.250Z
Answers.LastActivityDate: 2016-08-01T21:00:02.250Z
Answers.UserDisplayName: Brad Bell
Body: <p>Did anybody successfully install Craft on Google Cloud SQL? Or on any MySQL engine with activated replication and active GTID mode?</p>
  
Tags: <mysql>
Title: Craft CMS with Google Cloud SQL as backend database
ThreadText: # Craft CMS with Google Cloud SQL as backend database
  
  (Asked by: username_0 on 2016-07-31)
  
  Did anybody successfully install Craft on Google Cloud SQL? Or on any MySQL engine with activated replication and active GTID mode?
  
  **Tags:** mysql
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2016-08-01. Score: 5
  
  Craft currently won't operate properly if you have GTID enabled because GTID enforces that every table involved in a SQL statements in one transaction have to utilize the same storage engine.
  
  While virtually all of Craft's tables use InnoDB as the storage engine, the `craft_searchindex` table is still on MyISAM, because InnoDB didn't add full-text support until MySQL 5.6 and Craft still supports back to MySQL 5.1.
  
  If you're running MySQL 5.6+ (which you should be because I don't believe GTID was introduced until 5.6), then you can manually change the storage engine of the `craft_searchindex` table from MyISAM to InnoDB and you shouldn't run into any issues.
  
  
  ---
  
  