Epic #68397

Make TYPO3 work with MySQL strict mode

Added by Morton Jonuschat over 4 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Database API (Doctrine DBAL)
Target version:
Start date:
2008-05-20
Due date:
% Done:

100%

Sprint Focus:

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.


Subtasks

Bug #67186: Impossible to save to tt_contentClosedMorton Jonuschat

Bug #18866: Cannot create page with Mysl in strict mode (STRICT_TRANS_TABLES)RejectedAlexander Opitz

Bug #52204: SQL error: Incorrect integer value: '' for column 'backend_layoutRejected

Bug #20052: SQL error: 'Incorrect integer value: '' for column 'storage_pid' at row 1' (pages:NEW499d21cdec168)Rejected

Bug #18821: Installer will not create any be_users if unsupported sql_mode is usedClosedAlexander Opitz

Bug #52358: can't login to backend or install tool with PHP 5.4.19 (Typo3-internal session handler broken)ClosedMorton Jonuschat

Bug #52206: Default-values for text-fieldsClosed

Feature #68407: Check for MySQL strict mode in install toolClosedMorton Jonuschat

Bug #68418: scheduler chokes on mysql strict modeClosedMorton Jonuschat

Bug #68562: Bool values need to be cast to integer for MySQL strict modeClosedMorton Jonuschat

Bug #68564: Data too long for column 'NEWid' at row 1ClosedMorton Jonuschat

Bug #68602: NULL values in records get transformed to FALSE on T3D importClosedMorton Jonuschat

Bug #66430: Avoid MySQL Warning in File Meta Index processClosed

Bug #69000: Functional Tests: Field 'tx_irretutorial_1ncsv_hotels' doesn't have a default valueClosedMorton Jonuschat

Bug #69004: RelationHandler->readList() removes items with value of 0Closed

Bug #69027: Use proper data sets in workspaces testsClosedOliver Hader

Bug #69030: Apply default values in DataHandler functional testsClosedOliver Hader

Bug #69031: Use proper data sets in category collection testsClosedMorton Jonuschat

Bug #69039: Functional Tests: NEWid generation in tests does not match coreClosedMorton Jonuschat

Bug #69043: Functional Tests: FAL/DataSet/LiveDefaultElements.csv doesn't define all NOT NULL fieldsClosedMorton Jonuschat

Bug #69044: Functional Tests: Tables cf_extbase_object and cf_extbase_object_tags missingClosed

Bug #69051: Functional Tests: DataHandling/*/DataSet/LiveDefaultElements.csv doesn't define all NOT NULL fieldsClosedMorton Jonuschat

Bug #69058: Functional Tests: EXT:impexp Fixtures don't include all NOT NULL fieldsClosedMorton Jonuschat

Bug #69059: Functional Tests: Workspaces/*/DataSet/LiveDefaultElements.csv doesn't define all NOT NULL fieldsClosedMorton Jonuschat

Bug #69071: MetaDataRepository doesn't set all required (NOT NULL) fieldsClosedMorton Jonuschat

Bug #69072: Functional Tests: EXT:extbase fixtures don't include all required (NOT NULL) fieldsClosedMorton Jonuschat

Bug #69060: Out of range value for column 'details_nr'ClosedMorton Jonuschat

Bug #69073: DataHandler Hook does not move transOrigDiffSourceField fieldClosedMorton Jonuschat

Bug #69085: transOrigDiffSourceField ignored by DatamapperClosedMorton Jonuschat

Bug #69084: Adding Objects with NOT NULL columns is brokenClosedMorton Jonuschat

Bug #69088: updateObject sets sys_language_uid to NULLClosedMorton Jonuschat

Bug #69089: Functional Tests: Extbase blog_example has unused NOT NULL fields in SQL schemaClosedMorton Jonuschat

Bug #69090: detachObjectFromParentObject() uses invalid values for the parentKey on has many relationsClosedMorton Jonuschat

Bug #69247: Inserting records fails when the model has a incompatible default valueClosedMorton Jonuschat

Task #69484: Run functional tests in MySQL strict modeClosedMorton Jonuschat


Related issues

Related to TYPO3 Core - Bug #89103: impexp: sql error when strict_mode is enabled on database server New 2019-09-06

History

#1 Updated by Andreas Fernandez over 4 years ago

Afaik types of values are not juggled anymore. Example: Store a bool into an INT will fail with Strict Mode enabled.

#2 Updated by Wouter Wolters over 4 years ago

  • Status changed from New to In Progress

#3 Updated by Benni Mack about 4 years ago

  • Status changed from In Progress to Closed

#4 Updated by DANIEL Rémy 3 months ago

  • Related to Bug #89103: impexp: sql error when strict_mode is enabled on database server added

Also available in: Atom PDF