TYPO3 Core

To me, this would possibly not solve all "strict" problems, but it looks like the Core wrongly checks for "no value" with `empty()` instead of actually checking for either non-existant key in the fieldArray (TCA) or for actual empty string (=== '') and this should be easily solvable.

I'd appreciate if the Core would run flawless with strict mode turned on.

Sidenote: using empty() in code should raise a red flag :)

Xavier Perseguers wrote:

Having this definition:

[...]

One can properly choose a "grade" in the selector and persist it. But as soon as the default empty option is selected (0), persisting the record fails with:

[...]

Somehow the 0 is detected as "empty" and transformed into an empty string when sent to the database.

We use

'eval' => 'int'

In addition, we always use the following with strict mode so that the field is also saved correctly if it is not displayed to the editor:

'default' => 0

Yes, we had this too. "default => 0" is a must.

I have the same problem. I actully tried to add an allowed object via Extbase to my model to prevent this bug. But it did not work, too.
'default'=> 0, won't work for me.
'eval' => 'int', in a TCA for rendertype 'selectSingle' won't work and does not make much sense.

The only help was the addition to [DB][default] in 'localConfiguration.php' with ` 'initCommands' => 'SET sql_mode=\'\';', `.

I'm receiving the same error for a field of type passthrough even after adding the 'default' => 0 (running on v11.5.24). Happens when creating an object without setting that property (ObjectStorage in model where default value is null)
A solution without turning off strict mode would be preferable. Setting sql_mode = '' worked for my problem too though.

Same here. Default value is set in TCA and in Domain Model.