[rt-users] Search results anomaly

[Kenneth Marshall]

Hi Jeff,

There is nothing here that indicates a problem. It looks
like an apples vs. oranges comparison by the time you include
the actual parameters of the search from the web interface
and the rt commandline interface and possible privilege and
ACL differences. You can use DB query logging to figure out
what SQL is being used in the web search or the commandline
rt and compare the output piece-wise to put yourself at ease.
Maybe look at the individual components of each of the two
tickets, as well.

Cheers,
Ken

On Mon, Apr 26, 2010 at 11:21:45AM -0400, Jeff Blaine wrote:
> Does anyone have any suggestions for how to go about
> figuring out what is wrong here?
>
> On 4/22/2010 2:09 PM, Jeff Blaine wrote:
>> RT 3.8.7
>>
>> A search for 'Content matches foo.com' is returning some tickets
>> and missing others that clearly have foo.com in the Content.
>>
>>> [root at rtsrv1 bin]# ./rt show 39 | grep foo.com | wc -l
>>> 1
>>> [root at rtsrv1 bin]#
>>> [root at rtsrv1 bin]# ./rt show 23 | grep foo.com | wc -l
>>> 67
>>> [root at rtsrv1 bin]#
>>
>> 23 shows up in the web search results.
>>
>> 39 does not.
>>
>> Any ideas?
>>
>>
>> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
>> Buy a copy at http://rtbook.bestpractical.com
>>
>
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> Buy a copy at http://rtbook.bestpractical.com
>