| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | bubthegreat(at)gmail(dot)com |
| Cc: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, 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 20:34:18 |
| Message-ID: | CAKFQuwbAxGPz4VLzDyVJ+aV5drcJD9pcBVcv=xUqN+s036tJRg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Oct 31, 2018 at 10:34 AM Mike Taylor <bubthegreat(at)gmail(dot)com> wrote:
> Even just a link to the documentation for those would be very helpful as a
> "Looking for this? It's <here>" for the special character documentation
> that David mentioned would have been extremely helpful IMHO.
>
Not sure where you are expecting this "link to the documentation" to
exist...
"SQL Syntax" is a top-level item in the Table of Contents of the
documentation; Under that "Constants" seems like the right thing to call
these hand-written literals so that seems adequate as well. Given your
background in programming languages I would expect those two headings to be
sufficient to point you to the correct location in the documentation to
learn how to write SQL literals. Everyone has unique experiences though
and that's why the lists exist. The -general list would be a more
appropriate place to make sure inquiries though as this isn't a bug.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2018-10-31 22:44:12 | BUG #15475: Views over CITEXT columns return no data |
| Previous Message | Mike Taylor | 2018-10-31 17:23:21 | Re: BUG #15474: Special character escape sequences need better documentation, or more easily found documentation |