MySQL MATCH AGAINST On Multiple Columns

6 minute read

MATCH (column) AGAINST (keyword)

Before use

InnoDB tables require a FULLTEXT index on all columns of the MATCH() expression to perform boolean queries

# migration
class AddFulltextIndexToCatalogsOnAncestry < ActiveRecord::Migration[5.1]
  def change
    add_index :catalogs, :ancestry, {
      name: 'fulltext_index_catalogs_on_ancestry',
      type: :fulltext,
      comment: "for MATCH AGAINST purpose"
    }
  end
end

VS other query function

LIKE

Catalog.where(ids.map{|id| "ancestry LIKE \'\%#{id}\%\'"}.join(' OR ')).count

(30.3ms) SELECT COUNT(*) FROM catalogs WHERE (ancestry LIKE ‘%16994%’ OR ancestry LIKE ‘%20029%’ OR ancestry LIKE ‘%20080%’ OR ancestry LIKE ‘%3000%’ OR ancestry LIKE ‘%3083%’ OR ancestry LIKE ‘%3941%’ OR ancestry LIKE ‘%3947%’) => 3170

REGEXP

Catalog.where('ancestry REGEXP ?', ids.join('|')).count

(86.6ms) SELECT COUNT(*) FROM catalogs WHERE (ancestry REGEXP ‘16994|20029|20080|3000|3083|3941|3947’) => 3170

MATCH AGAINST

Catalog.where('MATCH ancestry AGAINST (?)', ids.join(' ')).count

(9.9ms) SELECT COUNT(*) FROM catalogs WHERE (MATCH ancestry AGAINST (‘16994 20029 20080 3000 3083 3941 3947’)) => 3170

Reference

MySQL 8.0 Reference Manual / … / Boolean Full-Text Searches

MySQL Like multiple values

MySQL LIKE operator Vs MATCH AGAINST

Leave a Comment