---
title: "Breaking: #68562 - Bool values need to be cast to integer for MySQL strict mode"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:breaking-68562"
source: "Changelog/7.5/Breaking-68562-BoolValuesNeedToBeCastToIntegerForMySQLStrictMode.rst"
typo3-version: "7.5"
typo3-major: 7
type: "breaking"
issue: 68562
forge: "https://forge.typo3.org/issues/68562"
tags: ["PHP-API", "Database"]
rendered: "2026-09-18T17:00:34+00:00"
---

# Breaking: #68562 - Bool values need to be cast to integer for MySQL strict mode {#breaking-68562}

See [forge#68562](https://forge.typo3.org/issues/68562)

## Description {#description}

MySQL strict mode doesn't accept '' as a valid value to store in an integer
column if the MySQL server is running in strict mode.

mysqli_real_escape() casts boolean values to string using '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.

## Impact {#impact}

All TYPO3 CMS installations using MySQL as DBMS.

## Affected Installations {#affected-installations}

Installations where 3rd party extension are relying on `FALSE` being cast to ''
when they are storing boolean values in character type columns. In this case new
values will get stored as '0'

## Migration {#migration}

Adjust the code to either store boolean values in integer type columns or
manually cast the boolean value to string before storing it in the database.