Project

General

Profile

Actions

Bug #14742

closed

Install - Databanalyser - Compare

Added by Hans-Georg Althoff over 19 years ago. Updated over 18 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
-
Start date:
2005-05-18
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
3.8.0rc1
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

After do the Compare function,
I will always get the following result:

1 Changing fields

ALTER TABLE be_users CHANGE lang lang char(2) NOT NULL default '';
Current value: varchar(2) NOT NULL default ''

ALTER TABLE static_countries CHANGE cn_iso_2 cn_iso_2 char(2) NOT NULL default '';
Current value: varchar(2) NOT NULL default ''

ALTER TABLE static_countries CHANGE cn_iso_3 cn_iso_3 char(3) NOT NULL default '';
Current value: varchar(3) NOT NULL default ''

ALTER TABLE static_countries CHANGE cn_tldomain cn_tldomain char(2) NOT NULL default '';
Current value: varchar(2) NOT NULL default ''

ALTER TABLE static_countries CHANGE cn_currency_iso_3 cn_currency_iso_3 char(3) NOT NULL default '';
Current value: varchar(3) NOT NULL default ''

ALTER TABLE static_country_zones CHANGE zn_country_iso_2 zn_country_iso_2 char(2) NOT NULL default '';
Current value: varchar(2) NOT NULL default ''

ALTER TABLE static_country_zones CHANGE zn_country_iso_3 zn_country_iso_3 char(3) NOT NULL default '';
Current value: varchar(3) NOT NULL default ''

ALTER TABLE static_currencies CHANGE cu_iso_3 cu_iso_3 char(3) NOT NULL default '';
Current value: varchar(3) NOT NULL default ''

ALTER TABLE static_languages CHANGE lg_iso_2 lg_iso_2 char(2) NOT NULL default '';
Current value: varchar(2) NOT NULL default ''

ALTER TABLE static_languages CHANGE lg_typo3 lg_typo3 char(2) NOT NULL default '';
Current value: varchar(2) NOT NULL default ''

After execute this DB-instruction, the result is always the same. It seem that this instructions will be not executed.

With other ones it was working fine.

(issue imported from #M1088)


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 #1

Updated by Peter Russ over 19 years ago

Mysql version?

Actions #2

Updated by Hans-Georg Althoff over 19 years ago

mySQL 4.1.10a

Actions #3

Updated by Peter Niederlag over 19 years ago

this has been a known bug for a long time with mysql > 4.x, it actually should really be fixed now.

Are you really sure that u are using TYPO3 3.8rc1?
which OS are you using?

Actions #4

Updated by Michael Stucki over 19 years ago

This seems to be a totally different problem. Obviously the field type is tried to be change from varchar to char but I think char is not allowed by TYPO3. So I think it could be a problem of this extension....

Can anybody please have a look at that?

Actions #5

Updated by Hans-Georg Althoff over 19 years ago

I have Win XP SP2 and PHP 5.0.4

Actions #6

Updated by Peter Russ over 19 years ago

This MIGHT be a MySql problem.
But with the version mentioned THIS should BE NO PROBLEM.
Because Mysql changed the handling of varchar in Version 5.
But he has 4.1.10.
So I wonder WHY his Mysql delivers varchar and not char as by def of MySql varchar<4 letter will be converted to char.
But perhaps he has InnoDB installed?

Actions #7

Updated by Michael Stucki over 19 years ago

I have checked this. The field type "char" has always been allowed (at least in 3.7) and be_users.lang has always been a char field, so I really don't know what's wrong here.

I close the bug marking it as not reproducable - feel free to reopen it if you find more information about it...

Actions

Also available in: Atom PDF