DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25820>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25820 [PATCH] QueryParser not handling queries containing AND and OR [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[PATCH] QueryParser not |[PATCH] QueryParser not |handling queries containing |handling queries containing |AND and OR correctly |AND and OR ------- Additional Comments From [EMAIL PROTECTED] 2004-03-02 14:48 ------- How about this. It seems to me that the optimal way to approach this problem at this point is to change the patch to return an empty Query instead of a null one, after all. This way we get everything that Doug mentioned (no need to test results, and we remain compatible with previous versions). This way we also fix the bug that you identified in the first place, which is incorrect parsing of AND/OR query expressions, and we also get the solution to only prohibited terms being present in the query. What we do not get is the way of figuring out why a returned Query is empty... and you (Morus) even say that blank Queries will raise parser exceptions. So I suggest we patch QueryParser.jj without this last bit for now, and add support for that later. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
