MIME-Version: 1.0
References: <CANzqJaD0=V+Dh+mLLfLj4ECLHriAH122LiYaqKyAnWCAKCfa6A@mail.gmail.com>
 <CAKFQuwbdAm7=RziKxF+jQki0KXb-quan5fA3sfq8JKoDR3Jumw@mail.gmail.com>
 <CANzqJaCL_p2LmCAUPGUYxOJPN-iOs-JWbpU4ssH+rSw27DmvhA@mail.gmail.com>
 <CAKFQuwZhOgbn+wbDTRXyqON2AEJM-R_Na2yHjLD0r9V4a+Fx=Q@mail.gmail.com>
 <CANzqJaDTY0AEB2zxumCbDtZu_pVxcjWpf5FdSeGwShLM3SfVzg@mail.gmail.com>
 <730017.1718032111@sss.pgh.pa.us> <CANzqJaDqZtWfk=s1_886m7TzTMek87Qcefpns4WRBvjm-9f-_w@mail.gmail.com>
 <CAKFQuwY0UxAeuCQTYtpyxZ83O8D=g5nAT8_7pSRtEG-FaHsUpg@mail.gmail.com>
In-Reply-To: <CAKFQuwY0UxAeuCQTYtpyxZ83O8D=g5nAT8_7pSRtEG-FaHsUpg@mail.gmail.com>
From: Ron Johnson <ronljohnsonjr@gmail.com>
Date: Mon, 10 Jun 2024 13:51:50 -0400
Message-ID: <CANzqJaAF+C5nXL6ZU+KROMNBbYYWY6XT8QXHPuhnOm+whdEodA@mail.gmail.com>
Subject: Re: Escaping single quotes with backslash seems not to work
To: pgsql-general <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000007cff6e061a8cce7e"
Archived-At: <https://www.postgresql.org/message-id/CANzqJaAF%2BC5nXL6ZU%2BKROMNBbYYWY6XT8QXHPuhnOm%2BwhdEodA%40mail.gmail.com>
Precedence: bulk

--0000000000007cff6e061a8cce7e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Jun 10, 2024 at 11:42=E2=80=AFAM David G. Johnston <
david.g.johnston@gmail.com> wrote:

> On Mon, Jun 10, 2024 at 8:19=E2=80=AFAM Ron Johnson <ronljohnsonjr@gmail.=
com>
> wrote:
>
>>
>> "set standard_encoding_strings =3D on" is at the top, and there's no oth=
er
>> reference to it.
>>
>>
> Well, if they are not using E-strings for escapes then you have the answe=
r
> why v14 is broken.  Does it really matter why v9.6 apparently worked even
> though it should not have if that setting was also set to on?
>

It matters that *something broke* either between PG 9.6 and 14 *OR* the old
JDBC driver and the new JDBC driver, because the client end users are
HOPPING MAD.

(Don't ask why it wasn't caught in testing; that's beyond my control.)

--0000000000007cff6e061a8cce7e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Jun 10, 2024 at 11:42=E2=80=AFAM =
David G. Johnston &lt;<a href=3D"mailto:david.g.johnston@gmail.com">david.g=
.johnston@gmail.com</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"=
ltr"><div style=3D"font-family:arial,helvetica,sans-serif"><span style=3D"f=
ont-family:Arial,Helvetica,sans-serif">On Mon, Jun 10, 2024 at 8:19=E2=80=
=AFAM Ron Johnson &lt;<a href=3D"mailto:ronljohnsonjr@gmail.com" target=3D"=
_blank">ronljohnsonjr@gmail.com</a>&gt; wrote:</span><br></div></div><div c=
lass=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div=
 dir=3D"ltr"><div dir=3D"ltr"><br></div><div class=3D"gmail_quote"><div>&qu=
ot;set standard_encoding_strings =3D on&quot; is at the top, and there&#39;=
s no other reference to it.</div><div><br></div></div></div></blockquote><d=
iv><br></div><div style=3D"font-family:arial,helvetica,sans-serif">Well, if=
 they are not using E-strings for escapes then you have the answer why v14 =
is broken.=C2=A0 Does it really matter why v9.6 apparently worked even thou=
gh it should not have if that setting was also set to on?</div></div></div>=
</blockquote><div><br></div><div>It matters that=C2=A0<b>something broke</b=
>=C2=A0either between PG 9.6 and 14 <b>OR</b> the old JDBC driver and the n=
ew JDBC driver, because the client end users are HOPPING MAD.</div><div><br=
></div><div>(Don&#39;t ask why it wasn&#39;t caught in testing; that&#39;s =
beyond my control.)</div><div><br></div></div></div>

--0000000000007cff6e061a8cce7e--