Re: Searching for 2004/3/EC (for example)
From: Hilary Cotter (hilary.cotter_at_gmail.com)
Date: 01/13/05
- Next message: George Cheng [MSFT]: "RE: Multiple Index Catalogs on the same webserver?"
- Previous message: neilx: "Searching for 2004/3/EC (for example)"
- In reply to: neilx: "Searching for 2004/3/EC (for example)"
- Next in thread: neilx: "Re: Searching for 2004/3/EC (for example)"
- Reply: neilx: "Re: Searching for 2004/3/EC (for example)"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 13 Jan 2005 10:51:51 -0500
I don't understand your date convention, or is it even a date convention.
When IS sees something that looks like a date it will assume it is a date
and parse it as such.
however, you can merrily remove these numbers from your noise word list -
probably noise.dat or if you are querying in dutch noise.nld, and rebuild
your catalog.
you will have to stop IS to make this change.
-- Hilary Cotter Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html "neilx" <neil@efc.be> wrote in message news:1105626556.437811.279470@c13g2000cwb.googlegroups.com... > My documents contain a lot of references to regulations (laws) that are > formatted similarly to yyyy/nn/EC. It is a very common search string > for the users of the application. > > Indexing Service seems to break strings on forward slashes and then > check the resultant parts against the noise lists. This is fine when > the middle section is > 9, but not when 0 to 9. > > This means that the results of such searches appear to be random. E.g. > "2004/45/EC" returns correct results > "2004/3/EC" returns all results containing 2004/anything/EC > (the 3 could just as easily be any digit) > > I have found out that noise.dat contains the line: > > $ 0 1 2 3 4 5 6 7 8 9 > > and it is this that converts both the catalog entry and the search > string to 2004/anything/EC when using 0-9 as the middle section. > > So could I simply remove this line from noise.dat? Would that cause me > problems elsewhere? (excessive catalogs size, for example) > > Alternatively, could I modify the word breaking behaviour to recognise > the yyyy/nn/EC format (and any others that are relevant) and not break > it. If so, how would I go about doing that (or who would I get to do it > for me:-) > > Neil >
- Next message: George Cheng [MSFT]: "RE: Multiple Index Catalogs on the same webserver?"
- Previous message: neilx: "Searching for 2004/3/EC (for example)"
- In reply to: neilx: "Searching for 2004/3/EC (for example)"
- Next in thread: neilx: "Re: Searching for 2004/3/EC (for example)"
- Reply: neilx: "Re: Searching for 2004/3/EC (for example)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|