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

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