View Issue Details

IDProjectCategoryView StatusLast Update
0000808OXID eShop (all versions)4.07. Source code, Testpublic2012-12-10 13:45
Reporterdainius.bigelis Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
Status resolvedResolutionfixed 
Product Version4.1.0 revision 17976 
Fixed in Version4.1.1 revision 18442 
Summary0000808: Charset changed to UTF8 for database during update to 4.1.0
DescriptionIn the update.sql for updating shop to version 4.1.0 there is one incorrect line:
  ALTER SCHEMA CHARACTER SET utf8 COLLATE utf8_general_ci;

After such update, all elements (Tables, fields), which are created after the update, will have charset UTF8, what's incorrect.
This line should not be included in update.sql.
Additional InformationFix which returns database charset to latin1 will be prepared. Fix is needed only for those clients, who already executed the update.sql from UPDATE package (to version 4.1.0) and changed the charset of their DB to UTF8 and don't want to convert shop to UTF8.
TagsNo tags attached.
Theme
BrowserAll
PHP Version5.2.6
Database Version5.0.33

Relationships

related to 0001970 closeddainius.bigelis Collation problems after update to CE 4.4.0_28699 
related to 0001987 resolvedvilma_liorensaityte Collation changes during update from 4.0.0.0 to 4.4.0 

Activities

dainius.bigelis

2009-04-17 12:09

reporter   ~0000775

The charset of DB can be fixed using this line:
ALTER SCHEMA CHARACTER SET latin1 COLLATE latin1_general_ci;

Also found two more querries for separate fields, which can be corrupted during executing update.sql and changed DB charset. These can be fixed by running:
- for all editions:
 alter table oxpricealarm modify `OXARTID` char(32) character set latin1 collate latin1_general_ci NOT NULL default '';
- only for EE:
 alter table oxaddress modify `OXCOUNTRYID` char(32) character set latin1 collate latin1_general_ci NOT NULL;

all these fixes are collected to one script (different for each edition) and published separately.