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 part of the field value As Erik pointed out, this would have to be fixed in the grammar: QueryParser.jj -Yonik On 1/23/06, Yonik Seeley <[EMAIL PROTECTED]> wrote: > 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 philosophy... the parser must make > decisions about what is part of the field value so it can know where > it is in the grammar. > > Examples where the field value is just "bar": > foo:bar^2 > foo:bar~2 > foo:bar baz > > Now your particular case of ':' may be solvable, but the problem in > general is not. One must escape special characters to avoid > ambiguity. > > -Yonik > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
