| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "bubthegreat(at)gmail(dot)com" <bubthegreat(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15474: Special character escape sequences need better documentation, or more easily found documentation |
| Date: | 2018-10-31 16:40:59 |
| Message-ID: | CAKFQuwZqDz032iap1+yyWf+NLmW=0aV+NyUFB-hnrwx=gXJDsg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wednesday, October 31, 2018, PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:
> A simple table elaborating on
> the escapes for each special character would be incredibly helpful at
> determining how to translate those escapes for cleaning strings prior to
> insertion so those of us using postgresql can quickly write cleaning
> functions for data.
>
Translating escapes and writing cleaning functions should be a rare need
unless you are writing driver-level code. Applications should avoid caring
about either by avoiding dynamic sql altogether or using quote_* functions
or the format function.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gierth | 2018-10-31 16:51:43 | Re: BUG #15474: Special character escape sequences need better documentation, or more easily found documentation |
| Previous Message | David G. Johnston | 2018-10-31 16:35:51 | Re: BUG #15474: Special character escape sequences need better documentation, or more easily found documentation |