FullText Searching: The Dilemma
mkanat at bugzilla.org
Tue Jun 26 23:35:58 UTC 2007
On Tue, 26 Jun 2007 23:57:18 +1000 "Bradley Baetz" <bbaetz at acm.org>
> The 'best' option would have to be something like the old shadowdb
> code did - insert changes into a separate (innodb) table, then have a
> separate script put the data into a side myisam table, with format
> (bug_id, key, value) using REPLACE. Remember, its not just long_desc,
> its the summary field too, at least (isn't it?)
Right. It's short_desc that's the problem here, actually.
Because of all the tables in Bugzilla, I can't make the "bugs" table
MyISAM--we'd lose almost all the advantages of transactions.
> Anyone know how useful mysql's trigger support is for doing that
> stuff? Especially without having its next key locking get in the way?
Hrm...that might be a good idea, actually. I'm not sure
triggers are available before 5.0, though, and we currently only
However, if we could get that to work, that's probably the best
solution. The only problem being the MySQL version required.
> Or, of course, just recommend that large installs use
> postgres+tsearch? ;)
We don't even support tsearch, yet, actually.
Competent, Friendly Bugzilla Services. And Everything Else, too.
More information about the developers