This is frustrated by escaping the MySQL template used in the LIKE statement.
root@dev> create table foo(name varchar(255));
Query OK, 0 rows affected (0.02 sec)
root@dev> insert into foo values('with\\slash');
Query OK, 1 row affected (0.00 sec)
root@dev> insert into foo values('\\slash');
Query OK, 1 row affected (0.00 sec)
root@dev> select * from foo where name like '%\\\\%';
Empty set (0.01 sec)
root@dev> select * from foo;
+------------+
| name |
+------------+
| with\slash |
| \slash |
+------------+
2 rows in set (0.00 sec)
root@dev> select * from foo where name like '%\\\\%';
Empty set (0.00 sec)
root@dev> select * from foo where name like binary '%\\\\%';
+------------+
| name |
+------------+
| with\slash |
| \slash |
+------------+
2 rows in set (0.00 sec)
According to MySQL docs: http://dev.mysql.com/doc/refman/5.5/en/string-comparison-functions.html#operator_like
%\\\\% - the correct operand, but why doesn't it give a result?
EDIT: The database I'm testing in has character_set_database for utf8. To continue my research, I created the same setting in the database that has character_set_database set to latin1, and guess what works '%\\\\%'!
EDIT: The problem can be reproduced, and this is a field mapping problem. Details: http://bugs.mysql.com/bug.php?id=63829