0002945: Import SQL into ADMIN>SERVICE>TOOLS window import fails using UTF-8 SQL Files

ID	Project	Category	View Status	Date Submitted	Last Update

0002945	OXID eShop (all versions)	2. ----- eShop backend (admin) -----	public	2011-06-01 09:14	2012-12-07 10:26

Reporter	markus mueller	Assigned To
Priority	urgent	Severity	major	Reproducibility	always
Status	resolved	Resolution	no change required
OS	Linux	OS Version	Debian Lenny
Product Version	4.5.0 revision 34568
Fixed in Version	4.5.1 revision 38045

Summary	0002945: Import SQL into ADMIN>SERVICE>TOOLS window import fails using UTF-8 SQL Files
Description	We want to import / Update the language 2 description for our RU OXID Version. Typical command line which works from MYSQL Commandline (in BASH) or PHPMYADMIN fails if COPY / PASTE into the ADMIN / SERVICE / TOOL Window. It does not fail if each command is entered line by line. So the problem seems the UTF-8 interpretation of the Linefeed / CR of the used interpreter / parser.
Steps To Reproduce	Check the attached Screenshoots- and reproduce e.g. with this commands: (add a 3rd Language "2" for testing) UPDATE `oxcountry` SET `OXACTIVE` = 1,`OXISOALPHA3` = 'OTH',`OXTITLE_2` = ' - ??? ? ?????? -',`OXSHORTDESC_2` = '???',`OXLONGDESC_2` = '???????? ???? ?????, ???? ????? ?????? ??? ? ??????.' WHERE `oxcountry`.`OXTITLE` = 'Other country'; UPDATE `oxcountry` SET `OXACTIVE` = 1,`OXISOALPHA3` = 'DEU',`OXTITLE_2` = '????????',`OXSHORTDESC_2` = 'EU1',`OXLONGDESC_2` = '' WHERE `oxcountry`.`OXISOALPHA3` = 'DEU'; UPDATE `oxcountry` SET `OXACTIVE` = 1,`OXISOALPHA3` = 'AUT',`OXTITLE_2` = '???????',`OXSHORTDESC_2` = 'EU1',`OXLONGDESC_2` = '' WHERE `oxcountry`.`OXISOALPHA3` = 'AUT'; UPDATE `oxcountry` SET `OXACTIVE` = 1,`OXISOALPHA3` = 'CHE',`OXTITLE_2` = '?????????',`OXSHORTDESC_2` = 'EU1',`OXLONGDESC_2` = '' WHERE `oxcountry`.`OXACTIVE` = 1 AND `oxcountry`.`OXISOALPHA3` = 'CHE'; ----------
Additional Information	We have prepared the sql script properly and can use it w/o errors in PHPMYADMIN or from the mysql command line (Any Browser Firefox, IE8, Chrome) The Trouble is also not depending which editor was used before (notepad++ or cyrillic version of notepad) We presume there is some trouble with the correct parsing of the entered text in combination with line End Character(s) and UTF-8 Content.
Tags	Import, SQL, UTF-8
Attached Files	OX-BUG-SQL-IMPORTUTF8-pic01-03.jpg (363,222 bytes) OX-BUG-SQL-IMPORTUTF8-pic01-03.jpg (363,222 bytes) COUNTRY-SAMPLE.SQL.RU.SQL.txt (872 bytes) UPDATE `oxcountry` SET `OXACTIVE` = 1,`OXISOALPHA3` = 'OTH',`OXTITLE_2` = ' - нет в списке -',`OXSHORTDESC_2` = 'Мир',`OXLONGDESC_2` = 'Выберите этот пункт, если вашей страны нет в списке.' WHERE `oxcountry`.`OXTITLE` = 'Other country'; UPDATE `oxcountry` SET `OXACTIVE` = 1,`OXISOALPHA3` = 'DEU',`OXTITLE_2` = 'Германия',`OXSHORTDESC_2` = 'EU1',`OXLONGDESC_2` = '' WHERE `oxcountry`.`OXISOALPHA3` = 'DEU'; UPDATE `oxcountry` SET `OXACTIVE` = 1,`OXISOALPHA3` = 'AUT',`OXTITLE_2` = 'Австрия',`OXSHORTDESC_2` = 'EU1',`OXLONGDESC_2` = '' WHERE `oxcountry`.`OXISOALPHA3` = 'AUT'; UPDATE `oxcountry` SET `OXACTIVE` = 1,`OXISOALPHA3` = 'CHE',`OXTITLE_2` = 'Швейцария',`OXSHORTDESC_2` = 'EU1',`OXLONGDESC_2` = '' WHERE `oxcountry`.`OXACTIVE` = 1 AND `oxcountry`.`OXISOALPHA3` = 'CHE'; COUNTRY-SAMPLE.SQL.RU.SQL.txt (872 bytes)

Theme	Both
Browser	All
PHP Version	5.2.6
Database Version	any

markus mueller 2011-06-01 09:20 reporter ~0004669 Last edited: 2011-06-01 09:26	As seen - the Mantis BugTracker has its beef with UTF-8 codes as well. So i uploaded a 4 SQL line statment sample file for testing.

markus mueller 2011-06-01 09:29 reporter ~0004670 Last edited: 2011-06-01 09:32	Despite the queer display of the non Ascii UTF-8 Characters, the content in the Database is correct in Russian if the import of the SQL Statements is done line by line. We can workaround with other methods for rolling out the Russian Version of OXID 4.5. At least it stops quite a lot of customers to do the job right or us doing an Standard Module.

Linas Kukulskis 2011-07-14 16:43 reporter ~0004860	problem is with the first character in the file. its a BOM http://www.dotvoid.com/2010/04/detecting-utf-bom-byte-order-mark/ delete this symbol or prepare correctly script file and try again. everything must be OK.

View Issue Details

Activities