Project

General

Profile

Actions

Bug #76641

closed

Database compare and "NULL default NULL" is not recognized

Added by Pascal Dürsteler over 8 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Install Tool
Target version:
-
Start date:
2016-06-15
Due date:
% Done:

100%

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

Description

I have a case where a decimal field is needed, which has a default value of NULL, and can contain NULL values, to differentiate between 0.0 and NULL.

The definition is

price decimal(5,2) unsigned NULL default NULL

Database compare then shows said field under "change fields" as

CHANGE price price decimal(5,2) unsigned NULL default NULL; 
Current value: decimal(5,2) unsigned default NULL

However, using "unsigned default NULL" would not allow NULL values and will yield errors on inserting or updating records.


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #76508: Comparison of NOT NULL fields without a default value does not work in "Compare Database" tool if a field is not autoincrementClosed2016-06-07

Actions
Related to TYPO3 Core - Feature #77643: Reimplement SqlSchemaMigrationService using SchemaManagerClosedMorton Jonuschat2016-08-25

Actions
Actions

Also available in: Atom PDF