Project

General

Profile

Actions

Bug #37124

closed

db-compare should check for available storage-engines

Added by Stefan Neufeind over 12 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Database API (Doctrine DBAL)
Start date:
2012-05-12
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
4.4
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

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


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Feature #61132: Allow overriding database-storage-engineRejected2014-08-21

Actions
Actions

Also available in: Atom PDF