pg_prepared_statements
Hi,
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"
--
// Dmitry.
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/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
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
2016-06-03 7:37 GMT+03:00 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>:
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.
According to https://www.postgresql.org/docs/current/static/sql-prepare.html
"statement" is a text of statement without "PREPARE". So, the phrase
"PREPARE statement"
not absolutely clear.
And according to
https://www.postgresql.org/docs/current/static/sql-commands.html
the PREPARE is a SQL command, rather than SQL statement.
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
On 6/3/16 2:38 AM, Dmitry Igrishin wrote:
"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.According to https://www.postgresql.org/docs/current/static/sql-prepare.html
"statement" is a text of statement without "PREPARE". So, the phrase
"PREPARE statement"
not absolutely clear.
And according to
https://www.postgresql.org/docs/current/static/sql-commands.html
the PREPARE is a SQL command, rather than SQL statement.
Fixed
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs