You are reading a single comment by @Velocio and its replies. Click here to read the full conversation.
  • This is what the system thinks....

    Here's your comment: https://www.lfgss.com/comments/16031751/

    And the search index says:

    Cheers. Thinking of keeping it local and as shamelessly indolent as possible so though it's a repeat, how are we with [#inthepark](https://www.lfgss.com/search/?q=%23inthepark)
    
    'cheer':1 'indol':10 'inthepark':23 'keep':4 'local':6 'possibl':12 'repeat':18 'shameless':9 'think':2 'though':14
    

    Here's my comment: https://www.lfgss.com/comments/16031937/

    And the search index says:

    But it appears that the [#in_the_park](https://www.lfgss.com/search/?q=%23in_the_park) one was being treated like a search for [#in](https://www.lfgss.com/search/?q=%23in) and PostgreSQL seems to treat that like a pure English search... meaning `in` hits the stopword list. So I adjusted the hash tag to be [#inthepark](https://www.lfgss.com/search/?q=%23inthepark) and the search now runs, but I don't see the results.\r+
    
    'adjust':56 'appear':22 'chang':7,15 'cours':10 'english':46 'extern':107 'failur':103 'happen':115 'hash':58 'hit':50 'index':90,109 'intern':95 'inthepark':62 'lack':88 'like':32,43 'list':53 'littl':13 'll':120 'long':18 'look':121 'mean':48 'noth':8,126 'one':28 'park':27 'postgresql':38,97 'promis':125 'pure':45 'result':74,79 'run':67 'search':34,47,65,108 'see':72 'seem':39 'show':81 'stopword':52 'summertim':78 'tag':59 'treat':31,41 'typic':112 'updat':105 've':6 'websit':118 'weird':3 'whilst':124 'would':111
    

    You can see that inthepark is present in both. So it's not the English search... and the plain text version is also in that... perhaps it's that though... I need to remember how the hell I implemented hashtag searching.

About

Avatar for Velocio @Velocio started