Bug #76641
closedDatabase compare and "NULL default NULL" is not recognized
100%
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.
Updated by Gerrit Code Review about 8 years ago
- Status changed from New to Under Review
Patch set 12 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/49593
Updated by Gerrit Code Review about 8 years ago
Patch set 13 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/49593
Updated by Gerrit Code Review about 8 years ago
Patch set 14 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/49593
Updated by Gerrit Code Review about 8 years ago
Patch set 15 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/49593
Updated by Morton Jonuschat about 8 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 2ba08444c9cd7613c97e10b65fd53867565f205c.