On 2015-11-17, kkm <kkm5848(a)gmail.com> wrote:
Continuing to dig into this...
+---------+----------------------------+
| page_id | page_title |
+---------+----------------------------+
| 11974 | Adhikamasa |
| 11975 | Adhikamasa,_adhimasa |
| 7128 | AdhikamÄ sa |
| 6658 | AdhikamÄ sa,_adhimÄ sa |
| 11977 | Adhikara |
| 11978 | Adhikara_Nandi |
| 11976 | Adhikarana |
| 6660 | Adhikaraṇa |
| 6659 | AdhikÄ ra |
| 6661 | AdhikÄ ra_Nandi |
| 7126 | AdhikamÄ sa,_adhimÄ sa |
| 7117 | Adhikaraṇa |
| 7125 | AdhikÄ ra |
| 7118 | AdhikÄ ra_Nandi |
+---------+----------------------------+
Can you also show your client settings by giving "\s" to MySQL client?
Not sure if this is correct, but I came across
http://product.hubspot.com/bid/7049/MySQL-and-Unicode-Three-Gotchas
which suggested that the page_title field could be improperly encoded (as
varchar 255 instead of utf8).
I tried to do
ALTER TABLE page MODIFY page_title VARCHAR(255) CHARACTER SET utf8;
Don't. Probably your data got "double-encoded" as utf-8.
They were binary utf-8 and the upgrade tool (or whatever) decided
to re-encode them.
*IF* this is the case, I would mysqldump a whole database under
the UTF-8 client settings and then change character
set designations to "binary" and import it as binary into
the binary tables. Might work.
This problem was pretty often seen when upgrading from MySQL 3 to 4
Saper