Project

General

Profile

Actions
Copy link

Bug #54412

closed

Improve default value handling for NULL value fields

Added by Alexander Stehlik almost 11 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
FormEngine aka TCEforms
Target version:
6.2.0
Start date:
2013-12-14
Due date:
% Done:

100%

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

Description

Currently the default value handling for input fields that can be set to NULL (eval is set to null) is quite inconsistent when creating new records:

  • if mode is set to useOrOverridePlaceholder the field is NULL by default
  • if this setting is not used the default value is a non empty string

Additionally it is not possible to explicitly set a NULL default value.

It would be better to if the mode does not have any influence on the default value but if it is possible to set NULL as default.

When this is handled together with #53662 backward compatibility should not be a problem because currently new records will have NULL values by default but empty strings are stored in the database.

Files

screenshot_tca_config.png (48.6 KB) screenshot_tca_config.png Alexander Stehlik, 2014-03-05 23:30

Related issues 2 (0 open — 2 closed)

Related to TYPO3 Core - Bug #53662: DatabaseConnection INSERTquery does not allow NULL valuesClosed2013-11-15

Actions
Has duplicate TYPO3 Core - Bug #60487: File References override meta data with empty string per defaultClosedOliver Hader2014-07-23

Actions
Actions
Copy link

Also available in: Atom PDF