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
Unknown Object (File)
Fri, Dec 20, 5:51 PM
Unknown Object (File)
Thu, Dec 12, 2:10 PM
Unknown Object (File)
Wed, Dec 11, 12:15 AM
Unknown Object (File)
Fri, Dec 6, 5:33 PM
Unknown Object (File)
Fri, Dec 6, 12:26 PM
Unknown Object (File)
Sat, Nov 30, 2:25 PM
Unknown Object (File)
Fri, Nov 29, 12:17 PM
Unknown Object (File)
Nov 9 2024, 1:21 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