Feedback-ID: i76984098:Fastmail
Message-ID: <35fb2ff3-9915-40ca-a8c5-3e5f6c9dd7cd@aklaver.com>
Date: Mon, 10 Jun 2024 13:52:53 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Escaping single quotes with backslash seems not to work
To: Ron Johnson <ronljohnsonjr@gmail.com>,
 pgsql-general <pgsql-general@postgresql.org>
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>
 <CANzqJaAF+C5nXL6ZU+KROMNBbYYWY6XT8QXHPuhnOm+whdEodA@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <CANzqJaAF+C5nXL6ZU+KROMNBbYYWY6XT8QXHPuhnOm+whdEodA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/35fb2ff3-9915-40ca-a8c5-3e5f6c9dd7cd%40aklaver.com>
Precedence: bulk

On 6/10/24 10:51, Ron Johnson wrote:
> On Mon, Jun 10, 2024 at 11:42 AM David G. Johnston 
> <david.g.johnston@gmail.com <mailto:david.g.johnston@gmail.com>> wrote:
> 
>     On Mon, Jun 10, 2024 at 8:19 AM Ron Johnson <ronljohnsonjr@gmail.com
>     <mailto:ronljohnsonjr@gmail.com>> wrote:
> 
> 
>         "set standard_encoding_strings = on" is at the top, and there's
>         no other reference to it.
> 
> 
>     Well, if they are not using E-strings for escapes then you have the
>     answer 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.

What was the change in the JDBC driver version?

What is the error you are getting currently?

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

-- 
Adrian Klaver
adrian.klaver@aklaver.com