| From: | Kirk Wolak <wolakk(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Remove obsolete mention of backslashes as escapes |
| Date: | 2023-04-12 22:21:06 |
| Message-ID: | CACLU5mR0AT2yn_-JQFhZWR+V5r=k0J-VW=pyLea5s8ZkogvQ9A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Tue, Apr 11, 2023 at 3:54 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:
> The documentation in
>
> https://www.postgresql.org/docs/current/sql-syntax-lexical.html#SQL-SYNTAX-DOLLAR-QUOTING
> says that
>
> "While the standard syntax for specifying string constants is usually
> convenient,
> it can be difficult to understand when the desired string contains many
> single
> quotes or backslashes, since each of those must be doubled."
>
> But this has been obsolete ever since version 9.1, when
> "standard_conforming_strings"
> started to default to "on". It has confused at least one reader:
> https://dba.stackexchange.com/q/325850/176905
>
> So I propose to remove the mention of backslashes there.
>
> Yours,
> Laurenz Albe
>
+1 I like this.. It's more clear and more accurate!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2023-04-13 01:06:44 | Packaging Related Objects into an Extension |
| Previous Message | Daniel Gustafsson | 2023-04-12 14:22:21 | Re: Should 'sum(mvf)' read 'sum(mcv)'...? |