Timeline for SQL Server Full-Text Indexer with stoplists/stopwords
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 10, 2012 at 8:14 | vote | accept | Ruud van de Beeten | ||
| Dec 7, 2012 at 17:54 | answer | added | StrayCatDBA | timeline score: 2 | |
| Dec 7, 2012 at 17:02 | history | edited | Ruud van de Beeten | CC BY-SA 3.0 |
added 159 characters in body
|
| Dec 7, 2012 at 16:59 | comment | added | Ruud van de Beeten | @swasheck my problem is that the words in the stoplist are still used/ranked in the Semantic Search functions like 'SEMANTICKEYPHRASETABLE'. | |
| Dec 7, 2012 at 15:51 | comment | added | swasheck | Isn't it just acknowledging that there are stopwords/"noise words" in the string? The documentation notes that the FT engine still needs to note its position. My understanding of noise words is that they add no significance to the weight of the result. Searching for "ruud loves a centimeter" would return the same level of significance as "he loves it." I could be wrong, though. | |
| Dec 7, 2012 at 12:18 | history | edited | Ruud van de Beeten | CC BY-SA 3.0 |
Added extra queries
|
| Dec 6, 2012 at 13:52 | history | asked | Ruud van de Beeten | CC BY-SA 3.0 |