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: "Jesse Tayler" Received: from mail-qt1-f181.google.com ([209.85.160.181] verified) by selbstdenker.ag (CommuniGate Pro SMTP 6.3.3) with ESMTPS id 25410974 for webobjects-dev@wocommunity.org; Mon, 15 Feb 2021 15:15:06 +0100 Received-SPF: none receiver=post.selbstdenker.com; client-ip=209.85.160.181; envelope-from=jtayler@oeinc.com Received: by mail-qt1-f181.google.com with SMTP id z32so4863684qtd.8 for ; Mon, 15 Feb 2021 06:15:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oeinc-com.20150623.gappssmtp.com; s=20150623; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=Kf9i1TarLa5AgCtNQEXfSJW2zqZqjBcSrXL5UBD3nRo=; b=ELBoQyLerb3gj5Q4sbeLqk8d9irXAkETGVNwyuiCNO/wb50J1WIdJi4ZO15p6t7l8G 3NTlbXrZX5BdR5pVbBw4GUDCNaUC/QWgROflEIzZepHDOlLKsphj+EzyGN+aK8w6eYWI qzOn80ve2SGN9IxLhP72zG3OZDhQX+nMo+a5V81//30pInDnmbIiPwAci2U26jvSqaux n+r6YS/TqrvUz8Tbma/U6iaJBL+xJN06kN8GUn3u0yG7u/qdc+eZm3DdAKpdv1Yfy/62 bEfPVL9HgiUQ1tXXwIkDww2R+aBtj6a8QwNeiuAkIsmQtZERIbC+AXfcDOg4D3qIeKm7 R5xQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=Kf9i1TarLa5AgCtNQEXfSJW2zqZqjBcSrXL5UBD3nRo=; b=O7OZ9WpqC0q1xQ9nZjiiFIkkK9G9SwoAUcKYziqoWzJsSJaqAcVdHDNxdrN3w+xkxC KE1AWjunTd/OA4DO8UtdyaZXVB71ct5Z4nZGntxuqey7ot2YflUlWlAoPTAp3vOhce5U enl3CfThopVVPqSCWlL879qQP06rZymj8zjEPS8w6Lf+Wv6jXA1xM/V+pUcaAsm3zt0C eI5gOuISbSmbf/imSRX8m2PtHUpxzt+INe1O7gy1qLXRX5jaDMK2uJBJ7OeS3wKM5oSe 1NkQ3PZB3GKgMRH8/yfu3JVWTxjW8eFPGkVVoRhSer0m03K72nyxx+ORAMrs6TttTXOU zpOw== X-Gm-Message-State: AOAM533Dqw6VOeJ5EjxnTjo5lCQkrJfmU3hdjdEz6eNDS4Wmblw9Na88 A29qKJOFcNZnVS0wcIHIsBbffbLEbOJgrw== X-Google-Smtp-Source: ABdhPJzIhmc0F8Qo/YISRHMtO8hLgr/dh+uxVyiVwMzN9sURAvqge1oQ9FQToZNrKvddsJr6le1zDA== X-Received: by 2002:a05:622a:44b:: with SMTP id o11mr14114966qtx.229.1613398484911; Mon, 15 Feb 2021 06:14:44 -0800 (PST) Return-Path: Received: from [192.168.1.16] ([69.169.5.176]) by smtp.gmail.com with ESMTPSA id o3sm11702307qke.132.2021.02.15.06.14.44 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 15 Feb 2021 06:14:44 -0800 (PST) Content-Type: multipart/alternative; boundary="Apple-Mail=_884DBB6A-087F-4A77-8617-1D81985E72FD" Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.2\)) Subject: Re: [WO-DEV] EOQualifier.qualifierWithQualifierFormat ignores proper AND/OR precedence?!? Date: Mon, 15 Feb 2021 09:14:40 -0500 References: To: WebObjects & WOnder Development In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3654.60.0.2.2) --Apple-Mail=_884DBB6A-087F-4A77-8617-1D81985E72FD Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I think I=E2=80=99d expect that SQL and I=E2=80=99d guess you can put in = your own braces to be explicit. I typically generate qualifiers using the ERX qualifier classes, ERXKeys = and the .dot() method which is just great. I=E2=80=99d only use text if I were doing something that lends = specifically to string formats > On Feb 15, 2021, at 8:47 AM, OCsite = wrote: >=20 > Hi there, >=20 > is it normal that >=20 > EOQualifier.qualifierWithQualifierFormat("userType =3D 12 OR userType = =3D 6 AND subjectType =3D 3",null) >=20 > creates >=20 > (((userType =3D 12) or (userType =3D 6)) and (subjectType =3D 3)) >=20 > ? 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. >=20 > Thanks, > OC >=20 --Apple-Mail=_884DBB6A-087F-4A77-8617-1D81985E72FD Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 I = think I=E2=80=99d expect that SQL and I=E2=80=99d guess you can put in = your own braces to be explicit.

I typically generate qualifiers using the ERX qualifier = classes, ERXKeys and the .dot() method which is just great.

I=E2=80=99d only use = text if I were doing something that lends specifically to string = formats



On Feb 15, 2021, at 8:47 AM, OCsite <webobjects-dev@wocommunity.org> wrote:

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=_884DBB6A-087F-4A77-8617-1D81985E72FD--