#105666Nullable native time fields store "00:00:00" instead of null if value is unset
Description
Native datetime fields are autogenerated as NULLable since #97367 – but nullable behaviour is broken and not considered to be default-on by DataHandler and FormEngine.
Expected Behavior:
User enters "00:00:00"
Stores "00:00:00"
User enters ""
Stores null
Actual Behavior:
User enters "00:00:00"
Stores "00:00:00"
User enters ""
Stores "00:00:00"
Reviews 13
- 14.3 97064[TASK] Run the zero date tests on SQLite as well
- main 97058[TASK] Run the zero date tests on SQLite as well
- main 88836[BUGFIX] Align Extbase DateTime handling to FormEngine and DataHandler
- 13.4 88945[BUGFIX] Align Extbase DateTime handling to FormEngine and DataHandler
- 13.4 88785[BUGFIX] Treat 0 as a defined value for nullable datetime fields
- main 88658[BUGFIX] Treat 0 as a defined value for nullable datetime fields
- 12.4 87481[BUGFIX] Fix storage of empty implicitly nullable native datetime fields
- main 87294[BUGFIX] Remove inconvenient nullable checkbox from datetime elements
- 13.4 87411[BUGFIX] Remove inconvenient nullable checkbox from datetime elements
- 12.4 87410[BUGFIX] Remove inconvenient nullable checkbox from datetime elements
- 12.4 87279[BUGFIX] Streamline midnight vs null handling of time fields
- 13.4 87388[BUGFIX] Streamline midnight vs null handling of time fields
- main 87144[BUGFIX] Streamline midnight vs null handling of time fields
Related issues 7
- Bug #92900Unable to store "epoch start" on native datetime fields with dbtype
- Bug #97216Time value "midnight" (00:00) is not accepted
- Feature #97367Auto creation of database fields for TCA "datetime"
- Bug #102602Time input does not initialize 00:00 properly
- Bug #105777Remove useless nullable checkbox from datetime elements
- Bug #105817The fix for #105666 (streamline null and midnight for dbType datetime) was breaking in some cases, and also ignores the TCA default value for datetime
- Bug #106401Nullable integer based time fields store consider 0 as empty value