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
F14121335: D17673.diff
Fri, Nov 29, 12:17 PM
Unknown Object (File)
Sat, Nov 9, 1:21 PM
Unknown Object (File)
Oct 17 2024, 10:53 PM
Unknown Object (File)
Oct 16 2024, 5:34 AM
Unknown Object (File)
Oct 16 2024, 4:14 AM
Unknown Object (File)
Oct 6 2024, 4:14 PM
Unknown Object (File)
Sep 30 2024, 3:10 AM
Unknown Object (File)
Sep 29 2024, 3:57 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
Branch
search1
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 16435
Build 21870: Run Core Tests
Build 21869: arc lint + arc unit