Project

General

Profile

Actions

Bug #17243

closed

Install tool's DB compare shows wrong tables to update on MySQL 5 collation latin1_bin

Added by Jörg Wagner about 17 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Install Tool
Target version:
-
Start date:
2007-04-25
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.1
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

With MySQL 5 and the collation of the Typo3 db set to latin1_bin the install tool shows a lot of tables to be changed that actually are correct. This happens because the command "binary" in the Current value is not recognized correctly - e.g.:

ALTER TABLE be_groups CHANGE title title varchar(50) NOT NULL default '';
Current value: varchar(50) binary default ''

Thus the install tool thinks the table has to be altered.
Trying to update the tables with the install tool results in the same list being shown again.

True that it is not very intelligent to set the db's collation to latin1_bin, but the install tool should show a correct warning instead of showing wrong db updates that also do not change the situation when executed.

MySQL 5
(issue imported from #M5495)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #16276: Database Analyser - Compare proposes "ALTER ..... NOT NULL" again and againClosed2006-06-23

Actions
Actions

Also available in: Atom PDF