Re: pg_prepared_statements - Mailing list pgsql-docs

From Peter Eisentraut
Subject Re: pg_prepared_statements
Date
Msg-id 956686ed-b753-14af-dc58-53627a860d69@2ndquadrant.com
Whole thread Raw
In response to pg_prepared_statements  (Dmitry Igrishin <dmitigr@gmail.com>)
Responses Re: pg_prepared_statements
List 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


pgsql-docs by date:

Previous
From: Dmitry Igrishin
Date:
Subject: pg_prepared_statements
Next
From: Dmitry Igrishin
Date:
Subject: Re: pg_prepared_statements