Project

General

Profile

Actions

Feature #67301

closed

Don't suggest database alterations for functionally equivalent field types with DBAL

Added by Morton Jonuschat almost 9 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Category:
Install Tool
Target version:
-
Start date:
2015-06-05
Due date:
% Done:

100%

Estimated time:
PHP Version:
5.6
Tags:
Complexity:
Sprint Focus:

Description

When using the InstallTool with the DBAL extension a lot of database alterations will be suggested that can never be resolved due to MySQL specific field types.
When the extension DBAL is loaded accept field types that only differ in their storage space requirements as long as they are functionally equivalent. Example:

TINYTEXT -> VARCHAR is OK
TINYINT -> SMALLINT, INTEGER, BIGINT is OK
INTEGER -> BIGINT is OK
MEDIUMINT -> INTEGER is OK
MEDIUMINT -> SMALLINT is NOT OK

Especially integer types which have lower min/max values should still be migrated.

Also ignore length information for INT fields as this information is purely for display purposes and doesn't change anything in regard to the values that can be stored in the field. Also the display width is ignored when the value exceeds it.


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Epic #64459: Make TYPO3 run on PostgreSQLClosed2015-05-21

Actions
Blocked by TYPO3 Core - Bug #67445: ALTER TABLE ADD KEY / DROP KEY unsupportedClosedMorton Jonuschat2015-06-14

Actions
Actions

Also available in: Atom PDF