Bug #73002 | Parser broken? | ||
---|---|---|---|
Submitted: | 13 Jun 2014 18:57 | Modified: | 14 Jun 2014 4:39 |
Reporter: | Simon Booth | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.5.37 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[13 Jun 2014 18:57]
Simon Booth
[13 Jun 2014 20:27]
Peter Laursen
Not reproducible for me on MySQL 5.5.38 (official from Oracle as well as MariaDB same) on Win7/64bit: USE test; DROP TABLE IF EXISTS `users` ; CREATE TABLE `users` (`user` VARCHAR(50)); INSERT INTO `users` VALUES ('band@greatcaesarband.com'); SELECT * FROM users WHERE `user` = 'band@greatcaesarband.com'; /* returns user -------------------------- band@greatcaesarband.com */ Are you sure that what you experience is not an issue with your client interface? -- Peter -- not a MySQL/Oracle person
[14 Jun 2014 4:39]
MySQL Verification Team
I also can't repeat any problem. Why is this is a server parser problem, and why do you think the "and" within a string matters anything? It doesn't. Please show us exact command outputs from the mysql command line client.
[14 Jun 2014 4:39]
MySQL Verification Team
specifically: select hex(user) from users where user like '%band@greatcaesarband.com%';