Brian,
you have two options:
1. Use your own parser (just modify default)
2. Use replace function, like
postgres=# select to_tsvector( replace('qw/er/ty','/',' '));
to_tsvector
--
'er':2 'qw':1 'ty':3
(1 row)
Oleg
On Wed, 28 Jul 2010, Brian Hirt wrote:
I have som
Brian Hirt writes:
> I'm really confused about what "ALTER TEXT SEARCH CONFIGURATION dict DROP
> MAPPING FOR file" actually does. The documentation seems to make it sound
> like it does what I want, but I guess it does something else.
No, it doesn't affect the parser's behavior at all. So fo
Tom,
Thanks for the quick reply. Doing a frontend mapping was my next option since
I really don't care about / and the ability to search on it. Preventing the
parser from using the file tokenizer seemed like a better solution so I wanted
to go down that path first (there are other false hit
Brian Hirt writes:
> For example instead of the parser recognizing three asciiword it recognizes
> one asciiword and one file. I'd like a way to have the / just get parsed as
> blank.
AFAIK the only good way to do that is to write your own parser :-(.
The builtin parser isn't really configur
