BUG #13540: upsert is not good

Started by Nonameover 10 years ago2 messagesbugs
Jump to latest
#1Noname
jxliang999@126.com

The following bug has been logged on the website:

Bug reference: 13540
Logged by: alex
Email address: jxliang999@126.com
PostgreSQL version: 9.5alpha1
Operating system: windows7
Description:

I am glad that you add insert and update on conflict function. But I suggest
it to be "insert or update into table..." because this seems much more
beaufiful to a strict programmer, thanks!

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

#2Bruce Momjian
bruce@momjian.us
In reply to: Noname (#1)
Re: BUG #13540: upsert is not good

On Thu, Aug 6, 2015 at 12:48:24PM +0000, jxliang999@126.com wrote:

The following bug has been logged on the website:

Bug reference: 13540
Logged by: alex
Email address: jxliang999@126.com
PostgreSQL version: 9.5alpha1
Operating system: windows7
Description:

I am glad that you add insert and update on conflict function. But I suggest
it to be "insert or update into table..." because this seems much more
beaufiful to a strict programmer, thanks!

We had a long discussion about this and decided that the syntax needed
for the UPDATE portion could not be mixed in with the INSERT portion.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs