Re: CONTAINSTABLE - weird results - using "and not"
- From: "daniel.hirsch@xxxxxxxxx" <daniel.hirsch@xxxxxxxxx>
- Date: 10 Aug 2005 09:08:54 -0700
I did a little more research...and I am thinking that because I use a
wildcard "*" to indicate the column, if say I used
CONTAINSTABLE(ICDB.dbo.SearchTable, *, '(( "rte*" ) AND ( "billing*"
) AND ( "opt*" ) AND ( "editor*" )) and NOT ( "integer*" )')
Both rte, billing, opt, and editor would need to be in the same column
that integer is not in. So if rte, billing, opt, and editor were in
say the title column, and integer was in the description column...it
would not correctly filter out those records with integer in the
description.
Does this make sense? Any ideas?
.
- Follow-Ups:
- Re: CONTAINSTABLE - weird results - using "and not"
- From: John Kane
- Re: CONTAINSTABLE - weird results - using "and not"
- References:
- CONTAINSTABLE - weird results - using "and not"
- From: daniel.hirsch@xxxxxxxxx
- CONTAINSTABLE - weird results - using "and not"
- Prev by Date: CONTAINSTABLE - weird results - using "and not"
- Next by Date: How to pass an SQLServer object to a method
- Previous by thread: CONTAINSTABLE - weird results - using "and not"
- Next by thread: Re: CONTAINSTABLE - weird results - using "and not"
- Index(es):