Actions
Epic #68397
closedMake TYPO3 work with MySQL strict mode
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Database API (Doctrine DBAL)
Target version:
Start date:
2008-05-20
Due date:
% Done:
100%
Estimated time:
(Total: 0.00 h)
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.
Updated by Andreas Kienast over 9 years ago
Afaik types of values are not juggled anymore. Example: Store a bool into an INT will fail with Strict Mode enabled.
Updated by Wouter Wolters over 9 years ago
- Status changed from New to In Progress
Updated by Benni Mack about 9 years ago
- Status changed from In Progress to Closed
Updated by Rémy DANIEL about 5 years ago
- Related to Bug #89103: impexp: sql error when strict_mode is enabled on database server added
Actions