MySQL Bugs: #7916: Failed to insert Chinese Character into a table from query browser

Bug #7916	Failed to insert Chinese Character into a table from query browser
Submitted:	14 Jan 2005 21:08	Modified:	19 Feb 2005 20:54
Reporter:	Troy Wang	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.1.2	OS:	Windows (Windows XP Pro sp1)
Assigned to:		CPU Architecture:	Any

Description:
Environment:
Operating System: Windows XP pro with sp1a (English Version)
MySQL Server: 4.1
What I did:
I modified default-character-set as utf8 in my.ini. I created a table (by using MySQL Administrator tool 1.0.15) with Charset utf8 and Collation utf8_bin (same settings go to each column).
Now, I can run insert into table_1 (col1, col2) values (2, 'some_chinese_characters') from the query browser. But when I run select query against the table, I got question marks (?) instead of chinese characters. However, in the select result panel, I selected one and then change the ? to Chinese characters, then click apply changes button.
Next, I run same select query again, this time the Chinese character is displayed correctly.

How to repeat:
1. using administrator tool to create a table called test1, check charset as utf8 and utf8_bin in collation option field.
2. adding two coloumns: col1 (integer, not null, primary key), col2 (varchar(45), not null)
3. opening query browser to run insert into test1 (col1, col2) values (2, 'some_chinese_characters'), and then hit execute button
4. running select * from test1
5. ???? is displayed on col2.
6. selecting this row and edit it
7. changing the ? to a chinese character
8. clicking Apply Changes button
9. running select * from test1 again
10. corrected chinese characters are displayed in the result panel.

Thanks for reporting. Can you state the server version you are using?

An UTF8 issue has been fixed in the 4.1.8 server. So I would ask you to upgrade to MySQL Server 4.1.9 and also use the latest MySQL Query Browser 1.1.5

Please state if the problem still exists. I should be solved in these versions. 

Thanks a lot!

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".