Shooter7119 / sequel-pro

Automatically exported from code.google.com/p/sequel-pro
Other
0 stars 0 forks source link

problem with cyrillic fields (cp1251 charset) #1813

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. create database wit cp1251 charset and tables with string (cp1251)
2. insert some one row woth text  e.x "привет"
3. export as .sql
4. try to import sql file, created on step 3.
5. error ((( alll fields with cyrillic text is null and another problem

Sequel Po nightly build 4126
What version of OS X are you using? mac os x 10.8.5
What version of MySQL are you connecting to on the server? 5.0

Original issue reported on code.google.com by lazarev...@gmail.com on 17 Sep 2013 at 8:58

Attachments:

GoogleCodeExporter commented 9 years ago
Verified in r4096.

This happens only if the table has default charset latin1 and the column has 
charset cp1251.
Sequel Pro correctly imports the data but when viewing the table switches to 
latin1 encoding resulting in "?????".

As a workaround go to View > Database Encoding and select either utf8 or cp1251

Original comment by schlabbe...@gmail.com on 19 Sep 2013 at 7:07

GoogleCodeExporter commented 9 years ago
Yeah.  At the moment encoding is only handled at the table level, so mismatches 
between the table and column encodings can really cause problems.  We need to 
address this - shouldn't be *too* hard.

Original comment by rowanb@gmail.com on 19 Sep 2013 at 1:39