Issue Bug Closed

#37124db-compare should check for available storage-engines

Stefan Neufeind 05/12/12, 22:09 updated 10/02/18, 12:17

Description

Currently if you have MySQL with, for example, disabled InnoDB (for reasons out of scope of this ticket) db-compare will insist that db-changes are needed. But that storage-engine can’t be set since it is not available. So for the easy case TYPO3 might still want to leave it as is (MyISAM in the usual case).

Example:
ALTER TABLE tx_realurl_pathcache ENGINE=InnoDB;
Current value: ENGINE=MyISAM
ALTER TABLE tx_realurl_chashcache ENGINE=InnoDB;
Current value: ENGINE=MyISAM
ALTER TABLE tx_realurl_urldecodecache ENGINE=InnoDB;
Current value: ENGINE=MyISAM
ALTER TABLE tx_realurl_urlencodecache ENGINE=InnoDB;
Current value: ENGINE=MyISAM

Reviews 1