Issue Bug Closed

#76641Database compare and "NULL default NULL" is not recognized

Pascal Dürsteler 06/15/16, 12:15 updated 10/02/18, 11:10

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.

Reviews 1