From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
Cc: | "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Dictionary chaining and stop words |
Date: | 2007-08-29 14:42:55 |
Message-ID: | 317.1188398575@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> writes:
> There's clearly need for transforming a word and passing on the
> transformed version to the next dictionary. dict_thesaurus does exactly
> that by supporting a subdictionary which is called before invoking the
> thesaurus, but it should be generic capability not specific to any
> dictionary. Let's modify the lexize API so that a dictionary can:
> - Accept the word (and possibly input with something else)
> - Reject the word
> - Transform word into another (or pass on as is)
This doesn't seem to be enough to solve thesaurus' problem though.
The difficulty there is that (1) it wants to look at several words
at once, (2) it wants to know which words were rejected as stopwords.
If filtering happens before it then how can it do that?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Bartunov | 2007-08-29 14:45:10 | Re: Dictionary chaining and stop words |
Previous Message | NikhilS | 2007-08-29 14:40:47 | StringInfo misc. issues |