My goodness, VARBINARY sucks so much!
When I wan to run some SELECT statements on some tables, I always get a SQL query like SELECT *, HEX(`column`) AS `column` FROM `table` WHERE `other` LIKE UNHEX('%foo%') in tools like #Adminer (a PHP-based web-frontend I usually use to administrate my database server). This causes it that zero records are being found and the culprit here is the wrong/excessive use of VARBINARY instead of VARCHAR (string variable character length) and a proper collation like utf8_general_ci for all tables.
I don't know why you e.g. want to have non-alpha-numerical characters in URLs or keys?! Why on good Earth that? I think a #RFC states that such characters needs to be URL-encoded with %HEX-CODE to avoid interference with not so tolerative systems. For example, I sometimes like to know how many contacts my node knows for a specific domain, so I usually choose LIKE %% and enter the domain name to look for. It worked always flawless before but since VARBINARY is in place, I can no longer find records. 
Very sad to see such development.
Roland Häder🇩🇪
in reply to Roland Häder🇩🇪 • •$ git blame view/global.cssthat the commit47ad922f9a1827e0f80f9ad473d821915abf4d60introduced this change.Friendica Support reshared this.
Roland Häder🇩🇪
Unknown parent • •view/global.css, was somit fuer alle Designs gilt.Friendica Support reshared this.
Roland Häder🇩🇪
Unknown parent • •Friendica Support reshared this.