Thread: UPSERT as a table name is confusing

UPSERT as a table name is confusing

From
Y Liu
Date:

It is really confusing to use UPSERT as a table name in a sql to demo the usage of INSERT INTO UPSERT...ON CONFLICT. How about using a different table name to show the same thing? Just a suggestion.

Thanks,
Eugene

Re: UPSERT as a table name is confusing

From
"Jonathan S. Katz"
Date:
On 8/15/22 8:41 AM, Y Liu wrote:
> RE: https://wiki.postgresql.org/wiki/UPSERT 
> <https://wiki.postgresql.org/wiki/UPSERT>
> 
> It is really confusing to use UPSERT as a table name in a sql to demo 
> the usage of INSERT INTO UPSERT...ON CONFLICT. How about using a 
> different table name to show the same thing? Just a suggestion.

The page in reference has the following line at the top:

"This Wiki page was only maintained until a few weeks before commit, 
where the patch further evolved in some minor aspects (most notably, the 
syntax became ON CONFLICT DO UPDATE/NOTHING). It is now only of historic 
interest."

(though the wiki is editable).

There are several examples in the docs here with less confusing labeling:

https://www.postgresql.org/docs/current/sql-insert.html

Thanks,

Jonathan

Attachment