Epic #68397

Make TYPO3 work with MySQL strict mode

Added by Morton Jonuschat 14 days ago. Updated 4 days ago.

Status:In Progress Start date:2008-05-20
Priority:Should have Due date:
Assigned To:- % Done:

91%
Category:Database API Spent time: -
Target version:7 LTS
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_contentResolvedMorton Jonuschat

Bug #18866: Cannot create page with Mysl in strict mode (STRICT_TRANS...RejectedAlexander Opitz

Bug #52204: SQL error: Incorrect integer value: '' for column 'backen...Rejected

Bug #20052: SQL error: 'Incorrect integer value: '' for column 'stora...Rejected

Bug #18821: Installer will not create any be_users if unsupported sql...ClosedAlexander Opitz

Bug #52358: can't login to backend or install tool with PHP 5.4.19 (T...ResolvedMorton Jonuschat

Bug #52206: Default-values for text-fieldsResolved

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

Bug #68418: scheduler chokes on mysql strict modeResolvedMorton Jonuschat

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

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

History

#1 Updated by Andreas Fernandez 14 days 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 4 days ago

  • Status changed from New to In Progress

Also available in: Atom PDF