From: Peter Eisentraut <peter_e@gmx.net>
Date: Sat, 19 Jan 2013 03:36:54 +0000 (-0500)
Subject: libpq doc: Clarify what commands return PGRES_TUPLES_OK
X-Git-Tag: REL9_3_BETA1~474
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=fb197290c1f25d8b7f35bc2bc7144eeaf603687c;p=postgresql

libpq doc: Clarify what commands return PGRES_TUPLES_OK

The old text claimed that INSERT and UPDATE always return
PGRES_COMMAND_OK, but INSERT/UPDATE with RETURNING return
PGRES_TUPLES_OK.

Josh Kupershmidt
---

diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index e7ad066fe5..d03ec40e33 100644
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -2469,7 +2469,8 @@ ExecStatusType PQresultStatus(const PGresult *res);
         command that happens to retrieve zero rows still shows
         <literal>PGRES_TUPLES_OK</literal>.
         <literal>PGRES_COMMAND_OK</literal> is for commands that can never
-        return rows (<command>INSERT</command>, <command>UPDATE</command>,
+        return rows (<command>INSERT</command> or <command>UPDATE</command>
+        without a <literal>RETURNING</literal> clause,
         etc.). A response of <literal>PGRES_EMPTY_QUERY</literal> might
         indicate a bug in the client software.
        </para>