String compare exact in query MySQL

There is no other fix for it. Either you specify a single comparison as being binary or you set the whole database connection to binary. (doing SET NAMES binary, which may have other side effects!)

Basically, that 'lazy' comparison is a feature of MySQL which is hard coded. To disable it (on demand!), you can use a binary compare, what you apparently already do. This is not a 'workaround' but the real fix.

from the MySQL Manual:

All MySQL collations are of type PADSPACE. This means that all CHAR and VARCHAR values in MySQL are compared without regard to any trailing spaces

Of course there are plenty of other possiblities to achieve the same result from a user's perspective, i.e.:

• WHERE field = 'abc ' AND CHAR_LENGTH(field) = CHAR_LENGTH('abc ')
• WHERE field REGEXP 'abc[[:space:]]'

The problem with these is that they effectively disable fast index lookups, so your query always results in a full table scan. With huge datasets that makes a big difference.

Again: PADSPACE is default for MySQLs [VAR]CHAR comparison. You can (and should) disable it by using BINARY. This is the indended way of doing this.

You can try with a regular expression matching :

SELECT * FROM barcode WHERE `code` REGEXP 'abc[[:space:]]'

i was just working on case just like that when using LIKE with wildcard (%) resulting in an unexpected result. While searching i also found STRCMP(text1, text2) under string comparison feature of mysql which compares two string. however using BINARY with LIKE solved the problem for me.

SELECT * FROM barcode WHERE `code` LIKE BINARY 'abc ';