InnoDB fulltext index

Dave Miller justdave at
Wed Sep 26 14:50:09 UTC 2012

Hash: SHA1

We already use fulltext indexing if using MySQL, so that part wouldn't
be new.  The only new part here is using InnoDB instead of MyISAM for
the table that has the fulltext index (which would eliminate a lot of
issues with the way we're doing the indexing and table management
right now, since everything in Bugzilla other than that table is InnoDB).

Unfortunately, Frédéric is right, we have to wait for most of the
distros to pick it up before we can make it a requirement (which
probably means waiting for Ubuntu 14.04 and RHEL 7).

yakoub wrote on 9/26/12 8:03 AM:
> fulltext index sql syntax is not compatible across different
> databases so code written for mysql won't run on postgres 
> web framework usually have search api interface like django
> haystack
> Frédéric Buclin wrote:
>> Le 26. 09. 12 08:12, Jochen Wiedmann a écrit :
>>> FYI: With MySQL 5.6, the InnoDB engine is now supporting full
>>> text indixes. Perhaps, this might be an opportunity for some
>>> code simplifications. Requiring 5.6 as the MySQL version seems
>>> fine to me.
>> MySQL 5.6 didn't reach the Release Candidate stage yet and so is
>> not stable. We cannot require 5.6 before a long time, because
>> older distros will still have an older version of MySQL. It will
>> probably take 2 years before we can require such a new version.
>> And before we require 5.6, we also have to make sure that MariaDB
>> also supports this feature.
>> LpSolit
>> - To view or change your list settings, click here: 
>> <>
> - To view or change your list settings, click here: 
> <>

- -- 
Dave Miller                         
System Administrator, Mozilla Corporation
Project Leader, Bugzilla Bug Tracking System
Version: GnuPG v1.4.5 (Darwin)
Comment: Using GnuPG with Mozilla -


More information about the developers mailing list