From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Escaping single quotes with backslash seems not to work |
Date: | 2024-06-10 14:12:57 |
Message-ID: | CAKFQuwYGJ-PoPr50SpWW3Dmn0_aG9TxCobDkjehP9uekOO+_og@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Jun 10, 2024 at 7:07 AM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Mon, Jun 10, 2024 at 7:02 AM Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
> 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 (\\). Also, a
>> single quote can be included in an escape string by writing \', in
>> addition to the normal way of ''.
>> [/quote]
>>
>>
> The link you provided goes to the wrong subsection.
>
Ah...you just linked to the section on constants where all the various
incarnations are subsections.
It would be a nice addition to include some examples in the section
pertaining to escape syntax. Make it more clear how it differs from just a
non-escaping literal. Maybe put something like \n into the basic literal
section showing that it outputs the literal two characters instead of a
newline.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Dominique Devienne | 2024-06-10 14:36:03 | libpq v17 PQsocketPoll timeout is not granular enough |
Previous Message | David G. Johnston | 2024-06-10 14:07:44 | Re: Escaping single quotes with backslash seems not to work |