On 6/10/24 10:51, Ron Johnson wrote:
On Mon, Jun 10, 2024 at 11:42 AM David G. Johnston
<david.g.johnston@xxxxxxxxx <mailto:david.g.johnston@xxxxxxxxx>> wrote:
On Mon, Jun 10, 2024 at 8:19 AM Ron Johnson <ronljohnsonjr@xxxxxxxxx
<mailto:ronljohnsonjr@xxxxxxxxx>> 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@xxxxxxxxxxx
