Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <h2>From <a href="http://dev.mysql.com/doc/refman/5.5/en/fulltext-boolean.html" rel="nofollow">MySQL docs</a></h2> <ul> <li><p><code>+</code> A leading plus sign indicates that this word must be present in each row that is returned.</p></li> <li><p><code>*</code> The asterisk serves as the truncation (or wildcard) operator. Unlike the other operators, it should be appended to the word to be affected. Words match if they begin with the word preceding the * operator.</p> <p>If a word is specified with the truncation operator, it is not stripped from a boolean query, even if it is too short (as determined from the ft_min_word_len setting) or a stopword. This occurs because the word is not seen as too short or a stopword, <strong>but as a prefix that must be present in the document in the form of a word that begins with the prefix</strong>. </p></li> </ul> <h2>In Context:</h2> <p><strong>MATCH(...) AGAINST(...)</strong> </p> <p><code>MATCH (name) AGAINST ('+ski*' IN BOOLEAN MODE)</code> means that you're searching for rows where a word in the <code>name</code> column <em>must contain</em> <code>ski</code>, and <em>must begin</em> with the word <code>ski</code>.</p> <p>From the set you've posted, <code>Dartmouth Skiway</code> is the only <code>name</code> that conforms to these requirements: it contains the word <code>ski</code>, and is prefixed by the word <code>ski</code>. </p> <p>The other <code>name</code> columns, though they match the first rule: <em>must contain <code>ski</code></em>, they are not <em>prefixed with</em> <code>ski</code>, as stipulated in your rule. The row returned by your boolean search is the only one with a <code>name</code> column that contains a word that both <em>contains</em> <code>ski</code> and is a word <em>prefixed</em> by <code>ski</code>.</p> <p>As suggested by ajreal, try decreasing the <code>ft_min_len_word_setting</code> in <code>my.cnf</code>. Your search might be failing to come up with the results you expect because of the default setting. Try reducing it to 3.</p> <p><strong>WHERE column LIKE %text%</strong></p> <p><code>WHERE name LIKE "%ski%"</code> searches for rows with <code>name</code> columns that contain <code>ski</code>, no matter where the word occurs.</p>
    singulars
    1. This table or related slice is empty.
    1. POMySQL Full Text Search Mystery
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMichael Robinson
    1. USMichael Robinson
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMySQL Full Text Search Mystery
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks for the thorough explanation! Can you suggest how I would update my original MATCH(...) AGAINST(...) query to perform an identical search to the LIKE query? I now understand the problem but am still not clear on the solution.
      singulars
      1. PO
      1. USRussell C.
    2. COIf you aren't worried about whether anything comes after `ski`, then you could try removing the `*`. This should mean "find rows with `name` columns that contain a word that starts with `ski`.
      singulars
      1. PO
      1. USMichael Robinson
    3. COThe problem I'm having is that no matter how I update the query it returns 0 results except in the form posted above. Could this have something to do with the ft_min_work_len as @ajreal suggested below?
      singulars
      1. PO
      1. USRussell C.
 

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