Re: '-' character not interpreted correctly in field names (solution)

2003-07-10 Thread Victor Hadianto
Okay attached is the diff file to allow t-shirt to be interpreted as "t-shirt". Queries that start with a "-" character behave as expected, well at least as we expected. For example: -shirt +pants as -shirt +pants One thing I need to mention is (I dig this from earlier discussion in this list

Re: '-' character not interpreted correctly in field names (solution)

2003-07-10 Thread Jan Agermose
+1 - Original Message - From: "Eric Jain" <[EMAIL PROTECTED]> To: "Lucene Users List" <[EMAIL PROTECTED]> Sent: Thursday, July 10, 2003 12:53 PM Subject: Re: '-' character not interpreted correctly in field names (solution) > > I think

Re: '-' character not interpreted correctly in field names (solution)

2003-07-10 Thread Eric Jain
> I think this is a fine change, that others would welcome, too. > No? > Does your change work with queries that start with a '-' character? > For example: -shirt +pants > (note: no space before '-shirt') > > If so, I think we could include this change in QueryParser.jj if you > send the diff, as

Re: '-' character not interpreted correctly in field names (solution)

2003-07-10 Thread Otis Gospodnetic
s the grammar that it should take all the > characters > > > except the ones you specified (the complement). > > > > > > Change: > > > | <#_FIELDNAME_START_CHAR: ( [ " ", "\t", "+", "-", "!", "(", &

Re: '-' character not interpreted correctly in field names (solution)

2003-07-09 Thread Victor Hadianto
;, ":", > > > > To: > > | <#_FIELDNAME_START_CHAR: ( ~[ " ", "\t", "+", "-", "!", "(", ")", ":", > > > > and it should probably work. > > > > Eric > > >

Re: '-' character not interpreted correctly in field names

2003-07-09 Thread Victor Hadianto
ot;?" ] > > > > > | <#_TERM_START_CHAR: ( ~[ " ", "\t", "+", "-", "!", "(", ")", ":", > > | "^", > > > > "[", "]", "

RE: '-' character not interpreted correctly in field names

2003-07-09 Thread Eric Isakson
t;, "-", "!", "(", ")", ":", To: | <#_FIELDNAME_START_CHAR: ( ~[ " ", "\t", "+", "-", "!", "(", ")", ":", and it should probably work. Eric -----Original Message----- From: Victo

Re: '-' character not interpreted correctly in field names

2003-07-09 Thread Victor Hadianto
so it will match the > "-" that you are using in your field names (and fix it to match any other > characters you want to use in field names that it doesn't allow right now). > > Eric > > -Original Message- > From: Jon Pipitone [mailto:[EMAIL PROTECTED] &

Re: '-' character not interpreted correctly in field names

2003-02-03 Thread Tatu Saloranta
On Monday 03 February 2003 07:19, Terry Steichen wrote: > I believe that the tokenizer treats a dash as a token separator. Hence, > the only way, as I recall, to eliminate this behavior is to modify > QueryParser.jj so it doesn't do this. However, doing this can cause some > other problems, like

Re: '-' character not interpreted correctly in field names

2003-02-03 Thread Terry Steichen
o: <[EMAIL PROTECTED]> Sent: Monday, February 03, 2003 2:39 AM Subject: '-' character not interpreted correctly in field names > Hello! > > I have a problem, a big one. I have successfully indexed 600 MB of XML > data, but the search can't give any results if the

'-' character not interpreted correctly in field names

2003-02-02 Thread hermit
Hello! I have a problem, a big one. I have successfully indexed 600 MB of XML data, but the search can't give any results if the field contains any '-' characters . For example: compound@cgx-code:[2 - 5] must match at least two results based on my XML data but it gives nothing. Can you advice