Re: BUG #13540: upsert is not good

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: jxliang999(at)126(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #13540: upsert is not good
Date: 2015-08-06 16:24:28
Message-ID: 20150806162428.GJ13687@momjian.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Aug 6, 2015 at 12:48:24PM +0000, jxliang999(at)126(dot)com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 13540
> Logged by: alex
> Email address: jxliang999(at)126(dot)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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Mark Simonetti 2015-08-07 11:32:38 Hang on NOTIFY
Previous Message jxliang999 2015-08-06 12:48:24 BUG #13540: upsert is not good