Databases
StackOverflow2013
Postsdbo
POMySQL LIKE operator with wildcard and backslash
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMySQL LIKE operator with wildcard and backslash
    primarykey
    data
    text
    <p>It's frustrated with MySQL's pattern escaping used in LIKE operator.</p> <pre><code>root@dev&gt; create table foo(name varchar(255)); Query OK, 0 rows affected (0.02 sec) root@dev&gt; insert into foo values('with\\slash'); Query OK, 1 row affected (0.00 sec) root@dev&gt; insert into foo values('\\slash'); Query OK, 1 row affected (0.00 sec) root@dev&gt; select * from foo where name like '%\\\\%'; Empty set (0.01 sec) root@dev&gt; select * from foo; +------------+ | name | +------------+ | with\slash | | \slash | +------------+ 2 rows in set (0.00 sec) root@dev&gt; select * from foo where name like '%\\\\%'; Empty set (0.00 sec) root@dev&gt; select * from foo where name like binary '%\\\\%'; +------------+ | name | +------------+ | with\slash | | \slash | +------------+ 2 rows in set (0.00 sec) </code></pre> <p>According to MySQL docs: <a href="http://dev.mysql.com/doc/refman/5.5/en/string-comparison-functions.html#operator_like" rel="nofollow">http://dev.mysql.com/doc/refman/5.5/en/string-comparison-functions.html#operator_like</a> <code>%\\\\%</code> is the right operand, but why it yields no result?</p> <p>EDIT: The database I'm testing that in has character_set_database set to utf8. To further my investigation, I created the same setup in a database that has character_set_database set to latin1, and guess what, <code>'%\\\\%'</code> works!</p> <p>EDIT: The problem can be reproduced and it's the field collation problem. Details: <a href="http://bugs.mysql.com/bug.php?id=63829" rel="nofollow">http://bugs.mysql.com/bug.php?id=63829</a></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USEnToutCas
    1. USEnToutCas
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMySQL LIKE operator with wildcard and backslash
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POMySQL LIKE operator with wildcard and backslash
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POMySQL LIKE operator with wildcard and backslash
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhen I use your commands exactly, `select * from foo where name like '%\\\\%';` works for me. I'm at a loss as to why it doesn't work for you though, I'm curious to know.
      singulars
      1. POMySQL LIKE operator with wildcard and backslash
      1. USmathematical.coffee
    2. COIt may have something to do with the database charset. I've updated the original post.
      singulars
      1. POMySQL LIKE operator with wildcard and backslash
      1. USEnToutCas
    3. COCheck this :- `select @@session.sql_mode; select @@global.sql_mode;`
      singulars
      1. POMySQL LIKE operator with wildcard and backslash
      1. USajreal
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload