Bug #16376
closed
Database Analyser always changes be_users lang field.
Added by Franz Holzinger almost 18 years ago.
Updated about 16 years ago.
Description
After the update for 4.0.0 I am asked continuouly in the Database Analyser to update the lang field.
Changing fields
ALTER TABLE be_users CHANGE lang lang varchar(2) NOT NULL default '';
Current value: char(2) default ''
(issue imported from #M3885)
Files
This works fine in my MySQL version, but I think I remember that I had the same problem with older versions.
If I remember correctly, this is (was) a bug in MySQL: Char fields cannot be changed into varchar.
Can you please try this out in phpmyadmin and let me know?
Even with phpMyAdmin it tells me that it did change the column successfully (see images), but in reality it did not change the lang field from char(2) to varchar(2).
phpMyAdmin 2.6.4-pl3
MySQL 4.1.12 sur le serveur localhost - utilisateur : root@localhost
Alright. So what do you want to do? In my opinion, we should just leave it as it is. It's a MySQL bug, and it has been fixed in a later version.
Ok. So we cannot change anything here.
When you close this item then in a way that it is still searchable and we do not get hundreds copies of it again.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
