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
I have some data that can be searched, and it looks like the parser is making
some assumptions about the data that aren't true in our case and I'm trying to
figure out how to exclude a token type. I haven't been able to find the
answer to my question so far, so I thought I would ask here.
Brian Hirt bh...@mobygames.com 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
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
Brian Hirt bh...@mobygames.com 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
