TYPO3 Core

Thanks for your report.

Especially 'nullable' => true was the most important one to avoid the SQl error. Isn't the core-default 'nullable' => true implicitly set if 'dbType' => 'datetime'? At least this is what happened implicitly up to 12.4.23. Did the change in #105666 alter this (intended or unintended)?

The v13 backport implied nullabe=true by default, but since we can not imply that `DEFAULT NULL` is used for native datetime fields in v12 we stayed with nullable=false as default intepretation if TCA does not configure it explicitly in v12.

Given the SQL schema, `nullable` => true is the correct TCA configuration.
I'll try to understand why this worked in your implicit usecase before. I had the perception that it should have always tried to persist 0000-00-00 00:00:00 in that case without explicit nullable=true configuration, but will check that…

We've got the same error messages on our servers running with MySQL 8.0.27-18 after the Update from 12.4.23 to 12.4.24.

2: SQL error: "SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value: '0000-00-00 00:00:00' for column 'product_launch_date' at row 1" (tx_myproducts_domain_model_product:40)

Error occures when the record is saved an has empty datetime fields.

-- ext_tables.sql
CREATE TABLE tx_myproducts_domain_model_product (
    product_launch_date datetime DEFAULT NULL,
    product_eol_date datetime DEFAULT NULL,

# TCA Field definition
        'product_launch_date' => [
            'label' => 'product_launch_date',
            'config' => [
                'dbType' => 'datetime',
                'type' => 'datetime',
                'size' => 12,
                'default' => null,
            ],
        ],
        'product_eol_date' => [
            'displayCond' => $displayconditionIn . $products['image-solution'] . ',' . $products['camera'] . ',' . $products['software'],
            'label' => 'product_eol_date',
            'config' => [
                'dbType' => 'datetime',
                'type' => 'datetime',
                'size' => 12,
                'default' => null,
            ],
        ],

After switching my ddev config from MariaDB 10.3 to mysql 8.0 I can also reproduce this error locally.

Update:
Adding 'nullable' => true, to the TCA configs solves the issue.

Patch set 2 for branch 12.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/87481

This affects v12 only.
I pushed a patch, please test the change to DataHandler in your installations, see:
https://review.typo3.org/c/Packages/TYPO3.CMS/+/87481/2/typo3/sysext/core/Classes/DataHandling/DataHandler.php

Thanks!

Patch set 3 for branch 12.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/87481