Search capabilities for different group types

Post Reply
Rodent
Posts: 90
Joined: Mon Dec 15, 2003 11:23 pm

Search capabilities for different group types

Post by Rodent »

I've noticed that if I do a subject search on e.g.

tangerine&mp3

or

tangerine|mp3

(mp3 = filename extension, not subject content)

in the same group, set up as respectively compact binary and msg-id direct, I get a lot of hits in the msg-id direct group, but none in the compact binary group.

Is that supposes to be that way?
alex
Posts: 4543
Joined: Thu Feb 27, 2003 5:57 pm

Post by alex »

you cannot change newsgroup type after creation, so check what are retention settings etc.

it just matches all entries for the pattern you provided, there is no difference (the same code and the same data structure as to quick filter related data), maybe you didn't download all headers so the matches are not there yet (you can sort by subject and look for matches from other view in the newsgroup where it doesn't give any matches).

to test it you also can create two instances of the same newsgroup with different destination types (just put different nicks so you can discern them).

btw. unrelated do you check the test area?
Rodent
Posts: 90
Joined: Mon Dec 15, 2003 11:23 pm

Post by Rodent »

alex wrote:you cannot change newsgroup type after creation, so check what are retention settings etc.
It's the same group set up in two different instances of UE, and there is the same header date range.

And no matter what, if it's an MP3 group then

anything|mp3

is supposed to get all headers containing an MP3 file, isn't it?

But I get none in the compact binary group. If I use "mp3" alone however, I get thousands of hits.

Integrity tests for both instances of UE returns "Succes", and Newsgroups are in order too.
Rodent
Posts: 90
Joined: Mon Dec 15, 2003 11:23 pm

Post by Rodent »

Well, I've just created two new instances of UE, setting up the group as respectively msg-id direct, and compact binary. I can't reproduce the problem here. So there must be some corruption in the database or something in the other instance.

Rodent
Post Reply