X-CGP-ClamAV-Result: CLEAN X-VirusScanner: Niversoft's CGPClamav Helper v1.22.2a (ClamAV engine v0.102.2) X-Junk-Score: 0 [] X-KAS-Score: 0 [] From: "OCsite" Received: from smtp-beta-2.zoner.com ([217.198.120.70] verified) by post.selbstdenker.com (CommuniGate Pro SMTP 6.3.3) with ESMTPS id 25410755 for webobjects-dev@wocommunity.org; Mon, 15 Feb 2021 14:47:34 +0100 Received-SPF: none receiver=post.selbstdenker.com; client-ip=217.198.120.70; envelope-from=ocs@ocs.cz Received: from smtp.zoner.com (smtp.zoner.com [217.198.120.6]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp-beta-2.zoner.com (Postfix) with ESMTPS id 5400D180047D for ; Mon, 15 Feb 2021 14:47:13 +0100 (CET) Received: from macbook-pro.ocsluj (smtp2stechovice.cli-eurosignal.cz [77.240.99.254]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: ocs@ocs.cz) by smtp.zoner.com (Postfix) with ESMTPSA id 26A073000096 for ; Mon, 15 Feb 2021 14:47:13 +0100 (CET) Content-Type: multipart/alternative; boundary="Apple-Mail=_2A0D38D4-CE6F-4131-8DAD-0F716639EE13" Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: EOQualifier.qualifierWithQualifierFormat ignores proper AND/OR precedence?!? Message-Id: <6B1BF764-81B5-4620-B88B-DFAC43C3AF3B@ocs.cz> Date: Mon, 15 Feb 2021 14:47:12 +0100 To: WebObjects & WOnder Development X-Mailer: Apple Mail (2.3608.80.23.2.2) --Apple-Mail=_2A0D38D4-CE6F-4131-8DAD-0F716639EE13 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi there, is it normal that EOQualifier.qualifierWithQualifierFormat("userType =3D 12 OR userType =3D = 6 AND subjectType =3D 3",null) creates (((userType =3D 12) or (userType =3D 6)) and (subjectType =3D 3)) ? Seems wrong, does it not? AND should always have higher operator = precedence than OR, should it not? I was just bit in my tender parts by = this, and I wonder whether this is the standard behaviour or some weird = quirk. Thanks, OC --Apple-Mail=_2A0D38D4-CE6F-4131-8DAD-0F716639EE13 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi = there,

is it normal = that

EOQualifier.qualifierWithQualifierFormat("userType =3D = 12 OR userType =3D 6 AND subjectType =3D 3",null)

creates

(((userType =3D 12) or = (userType =3D 6)) and (subjectType =3D 3))

? Seems wrong, does it = not? AND should always have higher operator precedence = than OR, should it not? I was just bit in my = tender parts by this, and I wonder whether this is the standard = behaviour or some weird quirk.

Thanks,
OC

= --Apple-Mail=_2A0D38D4-CE6F-4131-8DAD-0F716639EE13--