Bug #68562
closed
Epic #68397: Make TYPO3 work with MySQL strict mode
Bool values need to be cast to integer for MySQL strict mode
100%
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
Updated by Morton Jonuschat over 9 years ago
- Status changed from New to In Progress
Updated by Gerrit Code Review over 9 years ago
- Status changed from In Progress 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/41993
Updated by Morton Jonuschat over 9 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset cc72fd7e874c44bbd6ff6dd17c0b3ef6cdfb3623.
Updated by Christian Kuhn over 9 years ago
- Status changed from Resolved to New
patch was unfortunately reverted with https://review.typo3.org/#/c/42076/
Updated by Morton Jonuschat over 9 years ago
After discussion with Stefan Neufeind the initial implementation is still the best way to go, but the bug(s) in EXT:impexp need to be fixed first. Additionally this should be marked as breaking to be on the safe side.
Updated by Marc Bastian Heinrichs over 9 years ago
Link to the failing tests https://travis-ci.org/TYPO3/TYPO3.CMS/jobs/73080775
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/42376
Updated by Morton Jonuschat over 9 years ago
- Status changed from Under Review to Resolved
Applied in changeset 748c8294cba18966f3d4aa1370ebb8c8c2313376.
Updated by Riccardo De Contardi about 7 years ago
- Status changed from Resolved to Closed