Re: Handling of colons in QueryParserTokenManager

2006-01-24 Thread Erik Hatcher
On Jan 23, 2006, at 6:24 AM, Gwyn Carwardine wrote: It definitely was producing the error. I was very careful to test before I posted. But now, as you say, it doesn't do it. However, I wonder if I was entering ["Fred" TO "joe"] (note the capital F) because that IS still coming back with HTT

Re: Handling of colons in QueryParserTokenManager

2006-01-23 Thread Yonik Seeley
I just verified the behavior of an embedded ':' and I agree it's a problem that needs to be fixed because it currently silently truncates. foo:bar:baz is parsed as foo:bar foo:bar:baz:what is parsed as foo:bar The parser should either - throw an exception - treat ':' (and everything after) as p

Re: Handling of colons in QueryParserTokenManager

2006-01-23 Thread Yonik Seeley
On 1/23/06, Gwyn Carwardine <[EMAIL PROTECTED]> wrote: > the Token Manager's job is to parse into field & value, it shouldn't make > any decisions about the value; that value should get passed intact (complete > with colons and any other special characters) It's more a matter of parsing than philo

RE: Handling of colons in QueryParserTokenManager

2006-01-23 Thread Gwyn Carwardine
al characters) through to the Analyzer who's job it is to.. well.. analyse! Gwyn -Original Message- From: Erik Hatcher [mailto:[EMAIL PROTECTED] Sent: 23 January 2006 01:38 To: [email protected] Subject: Re: Handling of colons in QueryParserTokenManager On Jan 21, 2006,

Re: Handling of colons in QueryParserTokenManager

2006-01-22 Thread Erik Hatcher
On Jan 21, 2006, at 2:16 PM, Gwyn Carwardine wrote: Of course I think someone needs to go into the internals anyway... on 1.4.3 I get an index out of array bounds error (not a nice parse exception) when it tries to parse the following (which it should be able to do): ["fred" TO "joe"] Mayb

Re: Handling of colons in QueryParserTokenManager

2006-01-21 Thread Daniel Naber
On Samstag 21 Januar 2006 19:46, Chris Hostetter wrote: > if you are flexible in the syntax you are willing to support, you can > tell your users that they need to escape the colons that aren't ment as > field identifiers... > > ID:CI\:123 Or you could use a regular expression to turn ID:

RE: Handling of colons in QueryParserTokenManager

2006-01-21 Thread Gwyn Carwardine
t in to explain what on earth it's doing! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Hostetter Sent: 21 January 2006 18:46 To: [email protected] Subject: Re: Handling of colons in QueryParserTokenManager if you are flexible in t

Re: Handling of colons in QueryParserTokenManager

2006-01-21 Thread Chris Hostetter
u can avoid the whole painfull mess of the parser internals. : Date: Sat, 21 Jan 2006 13:10:56 - : From: Gwyn Carwardine <[EMAIL PROTECTED]> : Reply-To: [email protected] : To: [email protected] : Subject: Handling of colons in QueryParserTokenManager : : Hello, I'

Handling of colons in QueryParserTokenManager

2006-01-21 Thread Gwyn Carwardine
Hello, I'm new here. I've actually started using dotLucene but I think I need to make a change to the QueryParser but it's so complicated to try and understand what it's doing I thought I'd ask if maybe one of you guys could point me in the right direction? In my implementation of Lucene I have th