Project

General

Profile

Actions

Bug #59444

closed

DB Compare Fails Key sha1(40)

Added by Kay Strobach almost 10 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Must have
Category:
Install Tool
Target version:
Start date:
2014-06-10
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.4
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

During the Installation of TYPO3 i got a problem with that query:

ALTER TABLE sys_file ADD KEY sha1 (sha1(40));

Correcting it worked out:

-> Backticks ...
ALTER TABLE sys_file ADD KEY sha1 (`sha1`(40));

PS: There was a similar issue requesting backtick support, which was quite old ...


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Feature #68407: Check for MySQL strict mode in install toolClosedMorton Jonuschat2015-07-20

Actions
Actions #1

Updated by Kay Strobach almost 10 years ago

PS: MySQL 5.0 at Mittwald

Actions #2

Updated by Alexander Opitz almost 10 years ago

MySQL 5.1 is the minimum requirement for TYPO3 6.2. => https://github.com/TYPO3/TYPO3.CMS/blob/master/INSTALL.md

But yes, backtick support would be helpfull.

Actions #3

Updated by Kay Strobach almost 10 years ago

jigal said backticks will break dbal ...

Actions #4

Updated by Kay Strobach almost 10 years ago

then the DB Compare Tool should atleast show a warning if the mySQL version is to low ...

Actions #5

Updated by Morton Jonuschat almost 9 years ago

  • Category changed from Database API (Doctrine DBAL) to Install Tool
  • Assignee set to Morton Jonuschat
  • Target version changed from next-patchlevel to 7.5

A check for the minimum MySQL version in the Install Tool will be implemented after #68407

Actions #6

Updated by Gerrit Code Review almost 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/42368

Actions #7

Updated by Morton Jonuschat almost 9 years ago

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

Updated by Riccardo De Contardi over 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF