TYPO3 Core

Any news on this issue?

To understand what's happening it might be helpful to know the history how the current date-handling was first created:
http://xavier.perseguers.ch/en/tutorials/typo3/articles/native-date-type.html

It might be completely different now especially because of refactoring inside TYPO3.

This problem still exists in TYPO3 8. And on top of that: If you try to save an empty date (empty field), you get an error:

1: These fields of record 2 in table "tx_extensionname_domain_model_person" have not been saved correctly: date_of_birth! The values might have changed due to type casting of the database.

Christian,

I dare to say, the error is an issue with your extension. Probably it can be fixed by changes in database or TCA.
Have a look at the definitions in \ext_tables.sql and Configuration\TCA\mymodel.php above posted by Ralle Büchnitz, especially at 'default' and "geboren_am date DEFAULT '0000-00-00'".

Hi David, I dare to say that's not true. The exact above configuration will not allow you to save a record (form engine, not extbase) with an empty "geboren_am" field in TYPO3 8.7.1.
If you don't belive me, check out the well known extension styleguide. When you try to save the demo record with no date in inputdatetime_2 (which has the same configuration we talk about here, see TCA and sql), you'll get the same error I get in my extension.

I can confirm the problem of Christian.
Saving an empty date gives always the "The values might have changed due to type casting of the database." error.

It looks like the problem is some value casting, at least InputDateTimeElement.php always has $itemValue set to 0 instead of '0000-00-00' (which explains the error message).

Couldn't be reproduced in current master anymore.

I think it is still present in 8.7.9 - It is not possible to save a date prior to 01-01-1970 for example in the "start date" of fe_users. The error is still:

1: These fields of record 1 in table "fe_users" have not been saved correctly: starttime! The values might have changed due to type casting of the database.