I have BINARY(16) column in my table, but it's a surprise to me that phpMA tries to display it's contents as a text so I'm getting some unreadable garbage.
I would be more useful if phpMA could display mainly textual *_bin (i.e. utf8_bin) columns as a text not "[BLOB - * bytes]".
column with binary data
Logged In: YES
user_id=210714
Originator: NO
But your "path" field is a BLOB, correct?
Logged In: YES
user_id=2031724
Originator: YES
it's TEXT type with utf8_bin collation
Logged In: YES
user_id=210714
Originator: NO
About the utf8_bin field, MySQL returns in the flag informations that this field is binary. I'll continue my research and probably issue a MySQL bug report.
Logged In: YES
user_id=210714
Originator: NO
Part 1 of bug (TEXT utf8_bin should not be displayed as BLOB) fixed (for mysqli extension only) here:
http://phpmyadmin.svn.sourceforge.net/viewvc/phpmyadmin/branches/QA_2_11/phpMyAdmin/libraries/dbi/mysqli.dbi.lib.php?r1=11216&r2=11217
this will appear in 2.11.7.
Logged In: YES
user_id=210714
Originator: NO
Part 2 fixed (BINARY displayed as text) for 2.11.7.
Logged In: YES
user_id=210714
Originator: NO
Looks like some users want to display the contents of BINARY.
Maybe, to fit all situations, instead of the ShowBlob parameter, what we need is something like the big T icon, but has for effect of displaying the contents of all BINARY /BLOB fields.
Logged In: YES
user_id=210714
Originator: NO
In 3.0-dev, now a user can choose to display or not the contents of a BINARY or BLOB field.
Logged In: YES
user_id=210714
Originator: NO
The fix for not displaying BINARY as text is pushed to 3.0-dev, see bug 1988799.