Project

General

Profile

Actions
Copy link

Bug #68562

closed

Epic #68397: Make TYPO3 work with MySQL strict mode

Bool values need to be cast to integer for MySQL strict mode

Added by Morton Jonuschat over 9 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Morton Jonuschat
Category:
Database API (Doctrine DBAL)
Target version:
7 LTS
Start date:
2015-07-27
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
7
PHP Version:
5.6
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

MySQL strict mode doesn't accept '' as a valid value to store in an integer column if the MySQL is run in strict mode.
Boolean values are cast by mysqli_real_escape string to '1' (for TRUE) and '' (for FALSE). Due to this special handling is required for boolean values to result in '0' and '1' for FALSE/TRUE

Related issues 2 (0 open — 2 closed)

Related to TYPO3 Core - Bug #68418: scheduler chokes on mysql strict modeClosedMorton Jonuschat2015-07-21

Actions
Related to TYPO3 Core - Bug #68602: NULL values in records get transformed to FALSE on T3D importClosedMorton Jonuschat2015-07-29

Actions
Actions
Copy link

Also available in: Atom PDF