Project

General

Profile

Actions
Copy link

Bug #68994

closed

It is not possible to save NULL (replaced by the string "NULL")

Added by Sebastian Mazza over 8 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Extbase
Target version:
-
Start date:
2015-08-12
Due date:
% Done:

100%

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

Description

If a model property with any simple type (string, int, float, bool) is NULL, it will be replaced by the string literal 'NULL' before the update query is created.

I just replaced the following code:

if ($input === NULL) {
    return 'NULL';
}

with:
if ($input === NULL) {
    return null;
}

in TYPO3\CMS\Extbase\Persistence\Generic\Mapper\DataMapper::getPlainValue(...) and everything works fine, at least within my extension.

Related issues 2 (1 open — 1 closed)

Related to TYPO3 Core - Task #57255: Cleanup redundant code in extbase persistenceClosed2014-03-24

Actions
Related to TYPO3 Core - Bug #80119: Constraint Unique, Default null - String property ORMNew2017-03-03

Actions
Actions
Copy link

Also available in: Atom PDF