Open GoogleCodeExporter opened 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
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
Original issue reported on code.google.com by
lazarev...@gmail.com
on 17 Sep 2013 at 8:58Attachments: