Timeline for Using MATCH, AGAINST multiple times in MySQL fulltext search
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 14, 2019 at 8:13 | vote | accept | sdeav | ||
| Jan 11, 2019 at 23:41 | answer | added | Rick James | timeline score: 3 | |
| Jan 10, 2019 at 8:26 | comment | added | Akina | Create the final query variant and post it as self-answer. This can be useful to other participants with a similar problem. | |
| Jan 10, 2019 at 8:20 | comment | added | sdeav | @Akina. Thanks for your response. How can I select an answer?! | |
| Jan 10, 2019 at 8:14 | comment | added | Akina | MySQL version allows you to try MATCH .. AGAINST filtering in CTE and joining in main query. I think the condition selectivity is good enough for filtered recordset to be compact. in join or in WHERE clause? In join only, or the logic will be changed. | |
| Jan 10, 2019 at 8:00 | comment | added | sdeav | And which one will be best to use MATCH ... AGAINST in join or in WHERE clause? | |
| Jan 10, 2019 at 7:58 | comment | added | sdeav | 1) mysql.exe Ver 8.0.12 for Win64 on x86_64 (MySQL Community Server - GPL). 2) ok, i got it. So now using MATCH ... AGAINST 2 times. Is that ok?! | |
| Jan 10, 2019 at 7:37 | comment | added | Akina | 1) Specify your MySQL version. 2) MATCH ... AGAINST in WHERE clause seems to be excess - all records from tested tables which do not match are already ejected by join condition. | |
| Jan 10, 2019 at 6:55 | review | First posts | |||
| Jan 10, 2019 at 7:55 | |||||
| Jan 10, 2019 at 6:51 | history | asked | sdeav | CC BY-SA 4.0 |