Actions
Bug #60514
closed
Database analyzer does not parse TEXT null / not null fields
Status:
Closed
Priority:
Should have
Assignee:
Category:
Database API (Doctrine DBAL)
Target version:
-
Start date:
2014-07-24
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:
Description
Suppose you have a column defined as TEXT in a table, it will be implicit NULL.
CREATE TABLE fe_groups (
description text
);
If this column exists and the definition is later changed to "NOT NULL", the database analyzer does not recognize this change and thinks everything is fine.
CREATE TABLE fe_groups (
description text NOT NULL,
);
The db analyzer code should issue this command:
ALTER TABLE `fe_groups` CHANGE `description` `description` TEXT NOT NULL;
The same issue exists vice versa: If a field in NOT NULL and is changed to allow NULL as default.
Updated by
Actions