public inbox for [email protected]help / color / mirror / Atom feed
pg_prepared_statements 4+ messages / 2 participants [nested] [flat]
* pg_prepared_statements @ 2016-06-02 05:59 Dmitry Igrishin <[email protected]> 0 siblings, 1 reply; 4+ messages in thread From: Dmitry Igrishin @ 2016-06-02 05:59 UTC (permalink / raw) To: pgsql-docs 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 ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: pg_prepared_statements @ 2016-06-03 04:37 Peter Eisentraut <[email protected]> parent: Dmitry Igrishin <[email protected]> 0 siblings, 1 reply; 4+ messages in thread From: Peter Eisentraut @ 2016-06-03 04:37 UTC (permalink / raw) To: Dmitry Igrishin <[email protected]>; 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 ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: pg_prepared_statements @ 2016-06-03 06:38 Dmitry Igrishin <[email protected]> parent: Peter Eisentraut <[email protected]> 0 siblings, 1 reply; 4+ messages in thread From: Dmitry Igrishin @ 2016-06-03 06:38 UTC (permalink / raw) To: Peter Eisentraut <[email protected]>; +Cc: pgsql-docs 2016-06-03 7:37 GMT+03:00 Peter Eisentraut <[email protected]>: > 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 ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: pg_prepared_statements @ 2016-08-03 02:37 Peter Eisentraut <[email protected]> parent: Dmitry Igrishin <[email protected]> 0 siblings, 0 replies; 4+ messages in thread From: Peter Eisentraut @ 2016-08-03 02:37 UTC (permalink / raw) To: Dmitry Igrishin <[email protected]>; +Cc: 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 ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs ^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2016-08-03 02:37 UTC | newest] Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2016-06-02 05:59 pg_prepared_statements Dmitry Igrishin <[email protected]> 2016-06-03 04:37 ` Peter Eisentraut <[email protected]> 2016-06-03 06:38 ` Dmitry Igrishin <[email protected]> 2016-08-03 02:37 ` Peter Eisentraut <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox