Thx. So it is referring to the command not a "command returning no data". ;-)
On Wed, Sep 20, 2017 at 1:42 PM, John R Pierce <pie...@hogranch.com> wrote: > On 9/20/2017 10:34 AM, Igor Korot wrote: > > >From the documentation: > https://www.postgresql.org/docs/9.1/static/libpq-exec.html > > [quote] > PGRES_COMMAND_OK > > Successful completion of a command returning no data. > [/quote] > > No data = no rows, right? > > from that same page, a bit farther down, clarifying the potentially > confusing wording. > > If the result status is PGRES_TUPLES_OK, then the functions described below > can be used to retrieve the rows returned by the query. Note that a SELECT > command that happens to retrieve zero rows still shows PGRES_TUPLES_OK. > PGRES_COMMAND_OK is for commands that can never return rows (INSERT, UPDATE, > etc.). A response of PGRES_EMPTY_QUERY might indicate a bug in the client > software. > > > -- > john r pierce, recycling bits in santa cruz -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
