Subject: Re: pg_prepared_statements
To: Dmitry Igrishin <dmitigr@gmail.com>
References: 
 <CAAfz9KOFAKJCQn51XRMzQ+nakiVbZrdcA0c4BZ1LY5skeV1nyg@mail.gmail.com>
 <956686ed-b753-14af-dc58-53627a860d69@2ndquadrant.com>
 <CAAfz9KP7X7s08uCjF9-3fG8LERz0LLgt8FgY7fyxJdbztZTFNg@mail.gmail.com>
Cc: pgsql-docs <pgsql-docs@postgresql.org>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Organization: 2ndQuadrant
Message-ID: <4b05d90c-9b76-4be5-80e6-c4f7b8322bbc@2ndquadrant.com>
Date: Tue, 2 Aug 2016 22:37:00 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0)
 Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: 
 <CAAfz9KP7X7s08uCjF9-3fG8LERz0LLgt8FgY7fyxJdbztZTFNg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

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