By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,775 Members | 1,740 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,775 IT Pros & Developers. It's quick & easy.

Problem with tsearch and stopwords

P: n/a
Hi there,

I have an issue with tsearch. I'm using tsearch as a search mechanism on a
website making various queries created from the words that a user has put in.
So I query for all the words put in combined with a logical 'and' and also a
query with all the words combined with a logical 'or'. In the 'and' case
stopwords are correctly ignored whereas in the 'or' case they are not
apparently, e.g.

select 'tax&and&work'::mquery_txt;
mquery_txt
----------------
'tax' & 'work'
(1 row)

select 'tax|and|work'::mquery_txt;
NOTICE: Query contains only stopword(s) or doesn't contain lexem(s), ignored
mquery_txt
------------

(1 row)

Am I missing something? Is the only workaround to filter the stopwords myself
before I pass the query to tsearch?

Thanks

Joerg
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

Nov 11 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.