I am running into a version of this reported Drupal 7 issue: http://drupal.org/node/1089724
I get the following error when running Drupal with MyIsam.
"SQLSTATE[42000]: Syntax error or access violation: 1286 Unknown storage engine 'InnoDB'"
The patch in the issue mentioned above makes the following changes to the mysql database.inc file:
- // and invalid data handling. See http://drupal.org/node/344575 for further discussion.
- $this->exec("SET sql_mode='ANSI,TRADITIONAL'");
+ // and invalid data handling. See http://drupal.org/node/344575 for
+ // further discussion. Also, as MySQL 5.5 changed the meaning of
+ // TRADITIONAL we need to spell out the modes one by one.
+ $this->exec("SET sql_mode='ANSI,STRICT_TRANS_TABLES,STRICT_ALL_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER'");
Since this change was committed to core Drupal 7.10, can we either update dbtng to follow 7.10, or can we add this patch to the current dev version of dbtng.
If you opt to patch dbtng, I am happy to roll one for this issue.
Comments
Comment #1
apotek commentedOh, ok. Here's a patch for latest 6.x-1.x dbtng code. It resolves the error for me.
Comment #2
q0rban commentedLooks like the drupal 7 issue is over at http://drupal.org/node/1136854. This makes total sense, and should definitely be fixed. Thanks apotek for digging this up!
Comment #3
markdorisonThis looks good to me!
Comment #4
apotek commentedComment #5
ericduran commentedYep, I second the RTBC.
As mention before this was also a problem for D7 over at #1136854: MySQL 5.5 breaks speedy testing
Comment #6
mikey_p commentedThanks for this, I'm going to try to re-roll DBTNG as a backport from D7 head sometime in the next week or so, and if this change isn't included in that backport, I'll try the patch here.
Comment #7
apotek commented@mikey_p any news on whether we can backport this from D7 yet? The D7 issue was marked closed last September.
If you want me to roll a new patch against latest DEV, I can do that easily enough...