Rick Schumeyer writes:
> I also noticed that the directions for indexing multiple columns don't seem
> to be quite right.
> In section 12.2.2:
> UPDATE pgweb SET textsearchable_index_col =
> to_tsvector('english', coalesce(title,'') || coalesce(body,''));
Yeah, this would be better done wi
On Apr 17, 2009, at 7:02 AM, Rick Schumeyer wrote:
You can get extra (undesirable) results, depending on the name. For
example, if you are searching for the last name of "Ricks", you will
also find all authors whose first name is "Rick"
If you can process the names separately from the res
so it looks to me, like you are trying to use wrong tool for the job.
Why not just normalize names to #3 ?
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
You can get extra (undesirable) results, depending on the name. For
example, if you are searching for the last name of "Ricks", you will also
find all authors whose first name is "Rick".
I also noticed that the directions for indexing multiple columns don't seem
to be quite right.
In section 12.
Rick Schumeyer writes:
> I want to be able to search a list of articles for title words as well as
> author names. I understand how to do the title words with the full text
> searching. But I'm not sure the best strategy for the names. The full text
> parser "parses" the names giving undesirabl
Rick Schumeyer wrote:
> I want to be able to search a list of articles for title words as well
> as author names I'm not sure the best strategy for the names. The
> full text parser "parses" the names giving undesirable results.
>
> For example,
>
> select to_tsvector('claude Jones');
>
I want to be able to search a list of articles for title words as well as
author names. I understand how to do the title words with the full text
searching. But I'm not sure the best strategy for the names. The full text
parser "parses" the names giving undesirable results.
For example,
select
