Re: INSERT ON DUPLICATE KEY UPDATE - Mailing list pgsql-general

From Eduardo Pérez Ureta
Subject Re: INSERT ON DUPLICATE KEY UPDATE
Date
Msg-id 20040618204630.GA28564@localhost.localdomain
Whole thread Raw
In response to Re: INSERT ON DUPLICATE KEY UPDATE  (Robert Treat <xzilla@users.sourceforge.net>)
Responses Re: INSERT ON DUPLICATE KEY UPDATE  (Robert Treat <xzilla@users.sourceforge.net>)
List pgsql-general
On 2004-06-18 20:15:11 UTC, Robert Treat wrote:
> IIRC the standard syntax is based on db2's horrendous merge on command,
> which was only added to the standard a couple months back.

Great! I didn't know that was standard.
I see that Oracle has it:
http://www.dba-oracle.com/oracle_tips_rittman_merge.htm
And db2 as you said:
http://www.databasejournal.com/features/db2/article.php/3322041

Could you explain why db2's merge command is horrendous?
Is it better the mysql command?

So will postgresql accept this command?

> IIRC the main downside to the select/update method is it introduces a
> race condition that can only be solved by locking the table; not an
> issue for most my$ql apps but would be frowned upon by most postgresql
> users.

Or course, if you don't need to do locking is a plus.

Eduardo

pgsql-general by date:

Previous
From: jseymour@linxnet.com (Jim Seymour)
Date:
Subject: Re: INSERT ON DUPLICATE KEY UPDATE
Next
From: "Jeroen T. Vermeulen"
Date:
Subject: Article on open-source databases