Re: BUG #13540: upsert is not good - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: BUG #13540: upsert is not good
Date
Msg-id 20150806162428.GJ13687@momjian.us
Whole thread Raw
In response to BUG #13540: upsert is not good  (jxliang999@126.com)
List pgsql-bugs
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. +

pgsql-bugs by date:

Previous
From: jxliang999@126.com
Date:
Subject: BUG #13540: upsert is not good
Next
From: beijing_pg@163.com
Date:
Subject: BUG #13541: There is a visibility issue when run some DDL and Query. The time window is very shot