From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | jym(at)outlook(dot)com |
Cc: | "pgsql-docs(at)postgresql(dot)org" <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: Further Clarification request |
Date: | 2017-08-09 21:21:26 |
Message-ID: | CAKFQuwbv0RzFCtRUL+5VwVPOgjE4aPW0iPtD-nQQhTPzD9huHQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Wed, Aug 9, 2017 at 6:25 AM, <jym(at)outlook(dot)com> wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.6/static/sql-prepare.html
> Description:
>
> https://www.postgresql.org/docs/9.6/static/sql-prepare.html
>
> The first example: I'd like to see Hunter's Valley in the execute
> line as
> escaping isn't mentioned on the page or its links.
> Just a suggestion to help us beginners understand how things work.
>
This is one of hundreds of documentation examples that include literals.
Why is this one special that it needs to provide an example of a literal
containing a single quote that requires escaping?
The SQL Command section of the docs properly presumes the reader has
significant familiarity with writing SQL queries in PostgreSQL and is
looking either for understanding what the different kinds of commands are
or, more commonly, needs a refresher as to the exact syntax for less often
used commands.
More precisely, the vast majority of the docs assume you've read "Chapter
4. SQL Syntax".
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Jym Morton | 2017-08-09 22:21:11 | Re: Further Clarification request |
Previous Message | jym | 2017-08-09 13:25:26 | Further Clarification request |