#68397Make TYPO3 work with MySQL strict mode
Description
MySQL 5.6 defaults running in strict mode unless specifically configured otherwise. TYPO3 Core fails in a lot of places due to invalid, missing, or out of range values in DML statements such as INSERT, UPDATE, and DELETE.
MySQL 5.7 will probably put even more emphasis on strict mode due to NO_ZERO_DATE, NO_ZERO_IN_DATE and ERROR_FOR_DIVISION_BY_ZERO being part of the default strict mode.
The goal is to find and fix all places where the core breaks due to strict mode in time to be fixed for 7 LTS.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Subtasks 35
- Bug #18821Installer will not create any be_users if unsupported sql_mode is used
- Bug #18866Cannot create page with Mysl in strict mode (STRICT_TRANS_TABLES)
- Bug #20052SQL error: 'Incorrect integer value: '' for column 'storage_pid' at row 1' (pages:NEW499d21cdec168)
- Bug #52204SQL error: Incorrect integer value: '' for column 'backend_layout
- Bug #52206Default-values for text-fields
- Bug #52358can't login to backend or install tool with PHP 5.4.19 (Typo3-internal session handler broken)
- Bug #66430Avoid MySQL Warning in File Meta Index process
- Bug #67186Impossible to save to tt_content
- Feature #68407Check for MySQL strict mode in install tool
- Bug #68418scheduler chokes on mysql strict mode
- Bug #68562Bool values need to be cast to integer for MySQL strict mode
- Bug #68564Data too long for column 'NEWid' at row 1
- Bug #68602NULL values in records get transformed to FALSE on T3D import
- Bug #69000Functional Tests: Field 'tx_irretutorial_1ncsv_hotels' doesn't have a default value
- Bug #69004RelationHandler->readList() removes items with value of 0
- Bug #69027Use proper data sets in workspaces tests
- Bug #69030Apply default values in DataHandler functional tests
- Bug #69031Use proper data sets in category collection tests
- Bug #69039Functional Tests: NEWid generation in tests does not match core
- Bug #69043Functional Tests: FAL/DataSet/LiveDefaultElements.csv doesn't define all NOT NULL fields
- Bug #69044Functional Tests: Tables cf_extbase_object and cf_extbase_object_tags missing
- Bug #69051Functional Tests: DataHandling/*/DataSet/LiveDefaultElements.csv doesn't define all NOT NULL fields
- Bug #69058Functional Tests: EXT:impexp Fixtures don't include all NOT NULL fields
- Bug #69059Functional Tests: Workspaces/*/DataSet/LiveDefaultElements.csv doesn't define all NOT NULL fields
- Bug #69060Out of range value for column 'details_nr'
- Bug #69071MetaDataRepository doesn't set all required (NOT NULL) fields
- Bug #69072Functional Tests: EXT:extbase fixtures don't include all required (NOT NULL) fields
- Bug #69073DataHandler Hook does not move transOrigDiffSourceField field
- Bug #69084Adding Objects with NOT NULL columns is broken
- Bug #69085transOrigDiffSourceField ignored by Datamapper
- Bug #69088updateObject sets sys_language_uid to NULL
- Bug #69089Functional Tests: Extbase blog_example has unused NOT NULL fields in SQL schema
- Bug #69090detachObjectFromParentObject() uses invalid values for the parentKey on has many relations
- Bug #69247Inserting records fails when the model has a incompatible default value
- Task #69484Run functional tests in MySQL strict mode