diff options
| author | Peter Eisentraut | 2013-01-19 03:36:54 +0000 |
|---|---|---|
| committer | Peter Eisentraut | 2013-01-19 03:36:54 +0000 |
| commit | fb197290c1f25d8b7f35bc2bc7144eeaf603687c (patch) | |
| tree | 87a54228e999d1b3b8edf8d4a8bfaf82549029b3 /doc | |
| parent | c2a14bc7c994065edcc48183913a1fae2af27990 (diff) | |
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
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/src/sgml/libpq.sgml | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index e7ad066fe51..d03ec40e333 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> |