Hello,
It seems, that the statement "INSERT ... ON CONFLICT DO UPDATE tab SET
table_name.col = 1" is invalid in two ways. Patch attached.
Maybe it's worth to replace "UPDATE tab SET tab.col = 1" with "UPDATE
table_name SET table_name.col = 1" in ref/update.sgml (for consistency) too.
Best regards,
Alexander
diff --git a/doc/src/sgml/ref/insert.sgml b/doc/src/sgml/ref/insert.sgml
index e710cf4..0406a09 100644
--- a/doc/src/sgml/ref/insert.sgml
+++ b/doc/src/sgml/ref/insert.sgml
@@ -194,8 +194,8 @@ INSERT INTO <replaceable class="PARAMETER">table_name</replaceable> [ AS <replac
column leaves the other fields null.) When referencing a
column with <literal>ON CONFLICT DO UPDATE</>, do not include
the table's name in the specification of a target column. For
- example, <literal>INSERT ... ON CONFLICT DO UPDATE tab SET
- table_name.col = 1</> is invalid (this follows the general
+ example, <literal>INSERT INTO table_name ... ON CONFLICT DO UPDATE
+ SET table_name.col = 1</> is invalid (this follows the general
behavior for <command>UPDATE</>).
</para>
</listitem>
diff --git a/doc/src/sgml/ref/update.sgml b/doc/src/sgml/ref/update.sgml
index 35b0699..c50434f 100644
--- a/doc/src/sgml/ref/update.sgml
+++ b/doc/src/sgml/ref/update.sgml
@@ -123,7 +123,7 @@ UPDATE [ ONLY ] <replaceable class="PARAMETER">table_name</replaceable> [ * ] [
The column name can be qualified with a subfield name or array
subscript, if needed. Do not include the table's name in the
specification of a target column — for example,
- <literal>UPDATE tab SET tab.col = 1</> is invalid.
+ <literal>UPDATE table_name SET table_name.col = 1</> is invalid.
</para>
</listitem>
</varlistentry>
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
