From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Dmitry Igrishin <dmitigr(at)gmail(dot)com> |
Cc: | pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: pg_prepared_statements |
Date: | 2016-08-03 02:37:00 |
Message-ID: | 4b05d90c-9b76-4be5-80e6-c4f7b8322bbc@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2016-08-03 02:37:17 | Re: Inaccuracy in fe-protocol3.c |
Previous Message | Peter Eisentraut | 2016-08-02 23:25:51 | Re: Need clarification on "another server might be running; trying to start server anyway" |