Re: [GENERAL] Tsearch vector not stored by update/set

2005-03-22 Thread Justin L. Kennedy
On Mon, 21 Mar 2005, Andrew J. Kopciuch wrote: If you look at your config mappings for the default_english you will notice that you have 16 records, as opposed to 19 records like every other configuration mapping. From some more in depth observations, I noticed you are missing entries for the

Re: [GENERAL] Tsearch vector not stored by update/set

2005-03-21 Thread Andrew J. Kopciuch
It seems to be selective of only numbers, words with numbers in them, words with '.' or '/' characters. It completely ignores any other words or text in any of the 3 fields. This is a very big hint to your problem. You requested the pg_ts_* tables: On the Linux-redhat, pg7.3.2

Re: [GENERAL] Tsearch vector not stored by update/set

2005-03-21 Thread Justin L. Kennedy
On Sun, 20 Mar 2005, Andrew J. Kopciuch wrote: On Thursday 17 March 2005 17:55, you wrote: The short question is why does this: select to_tsvector('default', coalesce(name, '') ||' '|| coalesce(description, '') ||' '|| coalesce(keywords,'')) from link_items; give different results

[GENERAL] Tsearch vector not stored by update/set

2005-03-20 Thread Justin L. Kennedy
The short question is why does this: select to_tsvector('default', coalesce(name, '') ||' '|| coalesce(description, '') ||' '|| coalesce(keywords,'')) from link_items; give different results than this: update link_items set linksfti=to_tsvector('default', coalesce(name, '') ||' '||