On 6/10/24 10:51, Ron Johnson wrote:
On Mon, Jun 10, 2024 at 11:42 AM David G. Johnston
mailto:david.g.johns...@gmail.com>> wrote:
On Mon, Jun 10, 2024 at 8:19 AM Ron Johnson mailto:ronljohnso...@gmail.com>> wrote:
"set standard_encoding_strings = on" is at the top, and there's
On Mon, Jun 10, 2024 at 11:42 AM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Mon, Jun 10, 2024 at 8:19 AM Ron Johnson
> 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 esc
On Mon, Jun 10, 2024 at 8:19 AM Ron Johnson 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 ev
On 6/10/24 07:52, Ron Johnson wrote:
On Mon, Jun 10, 2024 at 10:08 AM David G. Johnston
mailto:david.g.johns...@gmail.com>> wrote:
This hasn't changed from 9.6, has it?
A Java app that uses backslash escapes broke this morning on fields with
single quotes, after the weekend migration from PG
On Mon, Jun 10, 2024 at 11:08 AM Tom Lane wrote:
> Ron Johnson writes:
> > On Mon, Jun 10, 2024 at 10:56 AM David G. Johnston <
> > david.g.johns...@gmail.com> wrote:
> >> As the caution on that page says the default for standard conforming
> >> strings changed in 9.1. But maybe your 9.6 had the
Ron Johnson writes:
> On Mon, Jun 10, 2024 at 10:56 AM David G. Johnston <
> david.g.johns...@gmail.com> wrote:
>> As the caution on that page says the default for standard conforming
>> strings changed in 9.1. But maybe your 9.6 had the old value configured but
>> when you upgraded to 14 you deci
On Mon, Jun 10, 2024 at 10:56 AM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Monday, June 10, 2024, Ron Johnson wrote:
>
>> On Mon, Jun 10, 2024 at 10:08 AM David G. Johnston <
>> david.g.johns...@gmail.com> wrote:
>>
>>> On Mon, Jun 10, 2024 at 7:02 AM Ron Johnson
>>> wrote:
>>>
On Monday, June 10, 2024, Ron Johnson wrote:
> On Mon, Jun 10, 2024 at 10:08 AM David G. Johnston <
> david.g.johns...@gmail.com> wrote:
>
>> On Mon, Jun 10, 2024 at 7:02 AM Ron Johnson
>> wrote:
>>
>>> PG 9.6 and PG 14
>>>
>>> https://www.postgresql.org/docs/14/sql-syntax-lexical.
>>> html#SQL-
On Mon, Jun 10, 2024 at 10:08 AM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Mon, Jun 10, 2024 at 7:02 AM Ron Johnson
> wrote:
>
>> PG 9.6 and PG 14
>>
>>
>> https://www.postgresql.org/docs/14/sql-syntax-lexical.html#SQL-SYNTAX-CONSTANTS
>>
>> [quote]
>> Any other character follow
On Mon, Jun 10, 2024 at 7:07 AM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Mon, Jun 10, 2024 at 7:02 AM Ron Johnson
> wrote:
>
>> PG 9.6 and PG 14
>>
>>
>> https://www.postgresql.org/docs/14/sql-syntax-lexical.html#SQL-SYNTAX-CONSTANTS
>>
>> [quote]
>> Any other character followi
On Mon, Jun 10, 2024 at 7:02 AM Ron Johnson wrote:
> PG 9.6 and PG 14
>
>
> https://www.postgresql.org/docs/14/sql-syntax-lexical.html#SQL-SYNTAX-CONSTANTS
>
> [quote]
> Any other character following a backslash is taken literally. Thus, to
> include a backslash character, write two backslashes (
PG 9.6 and PG 14
https://www.postgresql.org/docs/14/sql-syntax-lexical.html#SQL-SYNTAX-CONSTANTS
[quote]
Any other character following a backslash is taken literally. Thus, to
include a backslash character, write two backslashes (\\). Also, a single
quote can be included in an escape string by wr
12 matches
Mail list logo
