Project

General

Profile

Actions

Bug #57421

closed

Update database scheme still fails

Added by Nicole Cordes almost 10 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
Install Tool
Target version:
Start date:
2014-03-28
Due date:
% Done:

100%

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

Description

If you try to update a current 6.1 introduction package without any other core update the database scheme updater fails and blocks other updates.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #57805: SQL-ERROR: Specified key was too longClosed2014-04-10

Actions
Actions #1

Updated by Gerrit Code Review almost 10 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 https://review.typo3.org/28945

Actions #2

Updated by Nicole Cordes almost 10 years ago

  • Status changed from Under Review to New

To be more clear according to the identifier key issue:

in a current 6.1 installation of the introduction package the field length of identifier is 200. Within the update of the key "identifier" the length is set to 200 chars as well. This used to be okay, as within some 6.1 update the table field was raised to a length of 512 chars. Then the database index gets correctly cropped to 200 chars.

But coming from an elder not uptodate 6.1 installation the key is only set to the field without any cropping. This causes a problem for the field update to 512 chars as the index becomes to big. To solve this issue manual handling in the compare database wizard or even the database itself is needed.

Actions #3

Updated by Gerrit Code Review almost 10 years ago

  • Status changed from New to Under Review

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

Actions #4

Updated by Nicole Cordes almost 10 years ago

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

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF