AND/OR filter

Description

I am wondering if some of the parsing (filters in particular) should have a more relaxed parsing, for example case insensitive. We recently had an issue with the And/Or components of filter (they were AND OR).

Environment

None

Activity

Show:
codehaus
April 10, 2015, 4:38 PM

CodeHaus Comment From: cholmes - Time: Tue, 14 Dec 2004 12:35:37 -0600
---------------------
<p>I feel pretty strongly that we do not want relaxed parsing for things like this where the spec clearly states the format. Granted the spec does not really specify case sensitivity, but xml implies that cases are sensitive, so that they should explicitly state if it does not matter. And I think we want to enforce and promote the standards, and allowing clients to code against us being more lax, and then trying on a different server that matches the spec, would be a bad thing. </p>

<p>But this is a problem, I think the answer is to do much better pre emptive check against stuff like this, instead of returning bad results. If users instantly got a did you mean Or when they used an OR then I think this problem would go away.</p>

codehaus
April 10, 2015, 4:38 PM

CodeHaus Comment From: dblasby - Time: Tue, 17 May 2005 16:14:11 -0500
---------------------
<p>I made the parser might more likely to throw an error for these type of things. Still needs work in the DOM parser, though.</p>

codehaus
April 10, 2015, 4:38 PM

CodeHaus Comment From: aaime - Time: Thu, 29 Mar 2007 02:06:01 -0500
---------------------
<p>These issue has been in resolved state for at least one month (quite a bit, a lot more than one month). Batch transitioning them to closed state</p>

Fixed

Assignee

Unassigned

Reporter

codehaus

Triage

None

Fix versions

Affects versions

None

Priority

Medium
Configure