Project

General

Profile

Actions

Bug #53662

closed

DatabaseConnection INSERTquery does not allow NULL values

Added by Alexander Stehlik over 10 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
DataHandler aka TCEmain
Target version:
-
Start date:
2013-11-15
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.4
Tags:
Complexity:
no-brainer
Is Regression:
No
Sprint Focus:

Description

When you create a new record that has input fields with the new eval NULL setting the value is set correctly to NULL in the DataHandler but it is inserted as an empty string in the database.

The reason for this is, that the INSERTQuery() method in the DatabaseConnection class does not supply the $allowNull parameter to the fullQuoteArray() method. The UPDATEquery() method already does this so this can also be enabled for INSERTQuery().


Related issues 7 (0 open7 closed)

Related to TYPO3 Core - Feature #41773: Add possibility to store NULL valuesClosed2012-10-09

Actions
Related to TYPO3 Core - Bug #54917: Debug "Column 'first' cannot be null"Closed2014-01-12

Actions
Related to TYPO3 Core - Bug #54849: Functional tests cannot write to backend logClosedOliver Hader2014-01-08

Actions
Related to TYPO3 Core - Bug #55989: Debug "Column 'cookie' cannot be null"Closed2014-02-14

Actions
Related to TYPO3 Core - Bug #54412: Improve default value handling for NULL value fieldsClosed2013-12-14

Actions
Related to TYPO3 Core - Bug #63991: FAL override checkboxes are always active, when DBAL is installedClosed2014-12-19

Actions
Related to TYPO3 Core - Bug #81784: DatabaseConnection function INSERTmultipleRows does not allow NULL valuesClosed2017-07-04

Actions
Actions

Also available in: Atom PDF