Page MenuHomePhabricator

Fix a fulltext search issue where finding token length and stopwords could fail
ClosedPublic

Authored by epriestley on Apr 13 2017, 2:20 AM.
Tags
None
Referenced Files
F15515007: D17673.id.diff
Fri, Apr 18, 7:18 AM
F15512394: D17673.diff
Thu, Apr 17, 10:16 AM
F15459833: D17673.diff
Mon, Mar 31, 5:25 PM
F15458578: D17673.diff
Mon, Mar 31, 5:03 AM
F15423014: D17673.id42504.diff
Mar 22 2025, 12:07 PM
F15418152: D17673.id.diff
Mar 20 2025, 9:10 PM
F15401670: D17673.diff
Mar 17 2025, 6:45 PM
F15397313: D17673.id42505.diff
Mar 16 2025, 7:31 PM
Subscribers
None
Tokens
"Pirate Logo" token, awarded by epriestley.

Details

Summary

Ref T12137. If a database is missing the InnoDB or MyISAM table engines, the big combined query to get both will fail.

Instead, try InnoDB first and then MyISAM.

(I have both engines locally so this worked until I deployed it.)

Test Plan

Faked an InnoDB error like secure, got a MyISAM result.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable