I have a MySQL 5.0 database with unicode text in varchar and text fields with a utf8 character set. If I do a select in Toad (4.6 and 4.1) the results don't display as I would expect, ie, data from both fields shown as human-readable text, rather, the text fields are displayed as hex.Example:Table X in my DB includes the following fields:`A` text character set utf8 collate utf8_bin,`B` varchar(255) character set utf8 collate utf8_bin default NULL,If I do a select like:SELECT A, BFROM X;A is shown as hex like '0x596F756E672070...' while B is shown as readable text.If I alter the select as follows:SELECT A COLLATE utf8_unicode_ci, BFROM X;the A field displays readable text. The same thing happens if I use the utf8_bin collation in the select.Is displaying hex the intended/expected behaviour? And why does it display it as text if I apply a collation?
Message was edited by: Snapper1012
I am seeing the exact same thing. I was thinking that there must be an option to change the default view that grid displays for these text fields, but I am having trouble finding it. I found another thread dealing with this issue, but the members did not know the reason behind this default behavior nor did they know how to fix it. The best the other members could offer was to go back to "Toad for Mysql 4" as the default behavior was to display these fields in UTF8 (as opposed to hex). I've been searching high and low for a copy of Toad for Mysql 4.
Thanks, I'll check that out.