| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Dmitry Igrishin <dmitigr(at)gmail(dot)com>, pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: pg_prepared_statements |
| Date: | 2016-06-03 04:37:17 |
| Message-ID: | 956686ed-b753-14af-dc58-53627a860d69@2ndquadrant.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On 6/2/16 1:59 AM, Dmitry Igrishin wrote:
> I suggest to use phrase "the PREPARE SQL command" at
> https://www.postgresql.org/docs/current/static/view-pg-prepared-statements.html
> Thus, I would replace:
>
> "For prepared statements created via SQL, this is the PREPARE
> statement submitted by the client. For prepared statements created via
> the frontend/backend protocol, this is the text of the prepared
> statement itself."
> to
> "For prepared statements created via SQL, this is the PREPARE SQL
> command submitted by the client. For prepared statements created via
> the frontend/backend protocol, this is the statement itself."
>
> "true if the prepared statement was created via the PREPARE SQL statement"
> to
> "true if the prepared statement was created via the PREPARE SQL command"
I'm not sure why that is better. "statement" is the standard term in
these contexts.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitry Igrishin | 2016-06-03 06:38:16 | Re: pg_prepared_statements |
| Previous Message | Dmitry Igrishin | 2016-06-02 05:59:06 | pg_prepared_statements |