Project

General

Profile

Actions

Bug #68418

closed

Epic #68397: Make TYPO3 work with MySQL strict mode

scheduler chokes on mysql strict mode

Added by Anja Leichsenring over 9 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Should have
Category:
Database API (Doctrine DBAL)
Target version:
Start date:
2015-07-21
Due date:
% Done:

100%

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

Description

I run mysql Ver 14.14 Distrib 5.5.43, for debian-linux-gnu (x86_64) using readline 6.3, which contains the Strict mode handling introduced with mysql 5.6. So I run strict mode.

The scheduler gives error messages upon creating or updating scheduler tasks, containing messages like

caller => "TYPO3\CMS\Core\Database\DatabaseConnection::exec_INSERTquery" (60 chars)
ERROR => "Field 'lastexecution_failure' doesn't have a default value" (58 chars)

or

caller => "TYPO3\CMS\Core\Database\DatabaseConnection::exec_UPDATEquery" (60 chars)
ERROR => "Incorrect integer value: '' for column 'disable' at row 1" (57 chars)

and even Exceptions.

By adjusting my my.cnf file, commenting out the line STRICT_ALL_TABLES and restarting mysql, I got it to work.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #68562: Bool values need to be cast to integer for MySQL strict modeClosedMorton Jonuschat2015-07-27

Actions
Actions #1

Updated by Morton Jonuschat over 9 years ago

  • Category changed from 999 to Database API (Doctrine DBAL)
  • Assignee set to Morton Jonuschat
  • Target version set to 7 LTS
Actions #2

Updated by Gerrit Code Review over 9 years ago

  • Status changed from New to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/41994

Actions #3

Updated by Morton Jonuschat over 9 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
Actions #4

Updated by Riccardo De Contardi about 7 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF